Build and operate
Runners, gates, and recovery
Apply runner policy, review approvals, and recover failed or cancelled Build runs.
- Audience
- engineering leaders, developers
- Required role
- Engineering leader, developer, or approver with Build access.
- Product access
- Build
- Navigation path
- Build > Runners and Build runs > select a run
Outcome
Choose safe execution, make informed gate decisions, and recover without duplicating work.
Before you begin
- A work order ready for execution
- At least one healthy registered runner or cloud policy
Choose a runner
Match Local Runner or cloud execution to repository, credential, network, and data policy. Confirm runner health and allowed capabilities before starting.
Review a gate
Read the step output, diff, tests, and requested decision. Approve only when the evidence satisfies the gate; rejection feedback should be specific enough to guide the next step.
Cancel safely
Cancel when scope changes, unsafe behavior appears, credentials or environment are wrong, or continuing would waste usage. Record the reason and inspect partial output before restarting.
Retry or recover
Retry only recoverable failed steps. Correct the source cause first, then use the supported retry action so the run preserves history and avoids duplicating completed changes.
Related guides
Build Runs
Learn about workflows, gates, approvals, and isolated cloud execution.
Local Runner
Execute work orders on your own machine with your environment and credentials.
Work orders
Create execution-ready work from a plan and manage its delivery state.
Test plans and QA
Define test coverage, review revisions, and record QA completion for delivery work.