Runs
How individual job executions work — statuses, logs, and controls.
What Is a Run?
A run is a single execution attempt of a job. Every time a job fires — on schedule, manually triggered, or as a corrective retry — a new run record is created.
Run Statuses
| Status | Meaning |
|---|---|
deferred | Manually triggered for a future time; waiting to start |
queued | Waiting for an available executor slot |
running | Claude Code is actively executing |
succeeded | Completed successfully (exit code 0) |
failed | Completed with an error (non-zero exit code) |
permanent_failure | Pre-flight check failed (e.g. binary not found, project directory missing) |
cancelled | Cancelled by the user before or during execution |
Viewing Runs
Click any job to see its run history. Each run shows:
- Status and duration
- Start and finish timestamps
- Full stdout/stderr log stream
- Exit code and trigger source (scheduled, manual, or corrective)
Triggering Runs Manually
Click Run now on any job to immediately queue a run. Manual runs are given the highest priority and execute before any scheduled or corrective runs.
You can also defer a manual run to a specific future time — useful for queuing work without changing the job's recurring schedule.
Cancelling Runs
Click Cancel on any queued or running run:
- Queued runs — removed from the queue immediately
- Running runs — Claude Code receives SIGTERM; after a 5-second grace period, SIGKILL is sent if it hasn't stopped
Resuming Runs in Terminal
Every completed run records a Claude Code session ID. Click Open in Terminal on a completed run to launch Terminal, navigate to the project directory, and resume the session interactively with claude --resume <sessionId>. This lets you pick up where Claude Code left off or inspect what it did.
Clearing Run History
Run history is kept indefinitely. To clear history for a specific job, use Clear history in the job's settings menu.