Documentation

Recovery states, logs, and troubleshooting

Interpret retrying, cleanup-required, manual-attention, and failure states without treating them as generic “error” badges.

Try StackShiftRead the overview

Operations

Recovery states, logs, and troubleshooting

Live

Interpret retrying, cleanup-required, manual-attention, and failure states without treating them as generic “error” badges.

Goal

Use the new recovery-state model and logs together to diagnose operational problems accurately.

Current status

Live

This area is documented as current, user-reliable behavior.

Workflow

  1. 1Read the current operation or recovery state before retrying.
  2. 2Pair the state with recent logs and the last surfaced error.
  3. 3Use resource-level guides when the problem is obviously project-, stack-, node-, or database-specific.

Expected result

Recovery and failure states feel operationally useful instead of vague.

Common failures

  • Cleanup required after a blocked operation
  • Retryable failure with missing prerequisite
  • Logs show app/runtime issue rather than platform failure