Orchestration Ops

Transaction inspector and guarded replay-request controls (audit-only execute semantics).

Start Here

  1. Paste your `ADMIN_API_KEY` in Credentials, then click `Load`.
  2. Check `Operational Snapshot` first. Green means healthy, amber means warning, red means urgent.
  3. Use `Transaction Search` to filter by `flow`, `state`, or ID/key.
  4. Click a transaction to inspect its event timeline and request metadata.
  5. Only use replay controls during incident response: `Plan Replay` first, then `Record Approval` and `Record Execute Request` only if plan is allowed.

Legend

Transaction States
`started` / `in_progress`: currently running
`completed`: finished successfully
`failed`: failed with a clear error
`failed_ambiguous`: failed and outcome is uncertain
`compensation_failed`: rollback/compensation also failed
Flow Gate Row
`live`: successful live transactions counted
`anom`: anomalous live transactions (should be 0)
`stale`: long-running/unfinished transactions (should be 0)
`ready`: flow meets live gate criteria
`blocked`: flow currently fails gate criteria
Color Meaning
Green: healthy/pass
Amber: warning, watch closely
Red: failure/critical condition
Replay Controls
`Plan Replay`: risk + policy decision preview
`allowed=false`: request is denied by policy guardrails
`breakGlass`: required for terminal or risky states
`Record Execute Request`: audit record only in v1 (no automatic re-run)

Credentials

Transaction Search

Transactions

No transactions loaded

Selected Transaction

Select a transaction to inspect timeline and replay controls.
Status
Idle
Replay execute is audit-only in v1 (no automatic side-effect re-run).