Triage is designed to sit between a person and an AI coding agent. The fastest way to troubleshoot it is to capture the run ID and the point where the workflow stopped.
Run keeps reconnecting: refresh the Triage page and check that the runtime is healthy. A reconnect is designed to replay retained events rather than silently lose state.
A requirement was missed: send the correction through the same Triage run. The current specification version is authoritative; stale plans and stale verification cannot authorize delivery.
Delivery is blocked: inspect evidence, verification, safety state, and any approval requirement. A blocked delivery is intentional when the current artifact does not satisfy the active gates.
Use the runtime's /readyz and /healthz endpoints, retain the configured data directory in durable storage, and keep all secrets in deployment environment variables.
For the integration contract and security boundary, see integration details.