ralph-operations

To diagnose a stuck Ralph orchestration loop, list active loops, inspect loop logs, and diff state to understand the issue. Follow a structured workflow using commands to list, view logs, and stop loops for troubleshooting.

A Ralph loop post-mortem analysis identifies root causes of orchestration failures by inspecting logs and artifacts. Perform this analysis after a loop stops or fails to understand what went wrong in the execution lifecycle.

Monitor backpressure in Ralph loops by inspecting diagnostic data and loop status. Use commands to view logs and artifacts to detect when the system cannot handle incoming workload volume.

Yes, you can view state diffs for active Ralph orchestration loops. Use the diff command with a loop ID to compare current state against previous states, helping you debug hat selection and loop behavior.

The best way to triage Ralph loop issues is reading worktree artifacts and streaming logs. Start by listing active loops, inspect a specific loop with its ID, then view logs and diff state to pinpoint the failure.

Ralph loops may fail during hat selection due to state corruption or backpressure. Debug by inspecting diagnostic data, viewing logs, and diffing loop state to identify where the selection process broke down.