Documentation / Tools / Runs
Actions & Runs
How the run surface relates back to the broader actions-and-runs execution model in TrialStack.
Runs are the execution records. Actions & Runs is the broader operating model that explains how reusable automation definitions and their executions fit together.
Why it matters
- a reviewer starts from a run and needs the wider execution model
- teams need to connect one execution record back to the action that defined it
- operators want the conceptual frame behind run behavior
From each side
- Use Runs for execution-specific inspection.
- Use Actions & Runs for the wider model that joins actions and executions together.