Suspend, recover and execution history
Screen 5.7 — stop agents, track cancellation, reconcile external receipts and decide resumption explicitly.
PEEK Incident Operator · PEEK Technical Reviewer
/peek/customers/tenant-a/5-7Run history distinguishes stopped, completed, failed and outcome unknown. Disablement stops dependent queued work. Unknown outcomes are not failures eligible for blind retry: receipts are reconciled first (so a send that timed out is not sent twice) and every resumption records its authority.
5.7 · Suspend Recover & Execution History
Trace stops, incomplete runs and recovery. Open it at /peek/customers/tenant-a/5-7 (any tenant ID you can access works in place of tenant-a). The primary action is Suspend or stage recovery, which requires agent.restrict or recovery.review.
How 5.7 works
1. Inspect queued/running states, issue stop, track cancellation and reconcile external receipts before recovery
Screen 5.7 contract
- Fields shown
- Run state, cancellation result, external receipt, resumption decision
- Primary action
- Suspend or stage recovery
- Required capability
agent.restrictorrecovery.review- Validation
- Unknown outcomes are not failures eligible for blind retry; preserve idempotency identity and current permissions.
- Successful outcome
- Run history distinguishes stopped, completed, failed and outcome unknown; explicit resumption records authority.
- Screen states
- Loading; empty; ready; restricted; stale; error; review pending
- Audit event
admin.screen.5.7.action(acceptance testAT-UI-5.7)- Requirements
- R02, R06, R10, R16, R17, R28, R36, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-5.7
Related guides
Incidents, containment and recovery
Screens 8.5 and 8.6 — apply preauthorized containment immediately, then restore service only after current authority and technical checks.
Automation overview and agent templates
Screens 5.1 and 5.2 — review the permitted automation portfolio per tenant and release agent templates for agency adoption.