Skip to main content

Incident Debugging

Incident debugging starts from user-visible symptoms and works back to the affected workspace, artifact, route, operation, provider, or deploy.

Operator Workflow​

  • Capture what the user saw before changing state.
  • Identify the smallest failing surface.
  • Use timelines, events, and route checks to narrow cause.
  • Escalate with concrete refs and timestamps.

Verification Gates​

Verification gates: define the affected scope, run the relevant build or validation checks, perform the smallest appropriate deploy or config action, and verify the live user-facing or API behavior that changed.

For high-risk work, also prepare a rollback or follow-up plan before touching production.

Evidence To Capture​

  • Target environment and affected service, docs surface, API group, workspace, artifact, or operation.
  • Validation command or manual check performed.
  • Live route, API response, screenshot, or operation timeline proving the result.
  • Follow-up needed if verification is incomplete.

Media To Add​

  • Annotated workflow: symptom to route check to operation timeline to artifact/event evidence. It helps support teams triage incidents. Source: test incident drill.