TrialStack logo

Documentation / Tools

Runs

How teams inspect executions in TrialStack, understand progress, and decide whether a result should be retried, approved, or rejected.

See what actually happened

flowchart LR
    Action[Action] --> Run[Run]
    Run --> Artifact[Artifacts]
    Run --> Status[Status]

Runs are the execution record for automation in TrialStack. They show what happened, what is still in progress, and what output or artifacts a workflow produced.

Follow the attempt

A run gives the team a place to inspect:

  • status and queue-backed progress
  • the execution timeline
  • output artifacts and generated results
  • the difference between a clean completion, a failure, and an aborted attempt

Use runs for operational review

Open a run when:

  • a team needs to inspect one specific execution
  • operators need to understand failures, retries, or timing
  • reviewers need to decide whether a result is usable

Completion is not approval

A completed run only means the execution finished. Teams still need to judge the output quality, decide whether retry is useful, and keep approval decisions in the workflow that actually owns the result.