Results & restart
Runs execute locally on your PC; the server keeps a bounded summary per run — status, counts, and the last error — so every device can see the same progress.
Run summaries
- Status — Queued / Starting / Running / Stopping, then Succeeded / Failed / Cancelled / Skipped
- Processed, success, and failure counts, plus the current item label for batch runs
- The last error summary when something went wrong
Outcome labels
A failed run also carries a typed outcome so you know what to do next:
- DeadLetter — the run parked after repeated content failures; inspect, then restart
- JudgeUnavailable — the quality-judge infrastructure was unavailable; simply restart
- BreakerTripped — temporarily paused after repeated failures; wait and it re-arms itself
Restart (redrive)
Restart is offered only for terminal runs labelled DeadLetter or JudgeUnavailable. It resumes on the engine’s idempotent ledger, so anything the run already published is never published twice.
Note
A requested restart shows as pending until your desktop picks it up — the app never renders a dispatch as a completed run.
Repeat control
A repeating run can be turned off from any device. Re-arming a stopped run in place is not supported — start a new run instead.