debug

Trace stuck runs and execution failures in Symphony and Codex sessions by running `debug trace_session <session_id>` to identify the root cause. It correlates logs using issue identifiers to isolate the exact point of failure.

Diagnosing execution failures requires access to Symphony and Codex log files and specific session identifiers. You need the `issue_identifier`, `issue_id`, or `session_id` to correlate logs and isolate the underlying problem.

Log correlation for resolving stuck Symphony runs works by matching `issue_identifier`, `issue_id`, and `session_id` keys across trace outputs. This isolates specific session lifecycles and captures evidence for root cause analysis.

The best way to investigate execution failures in administrative and development environments is using a structured investigation flow. This classifies problems, validates scope, and captures evidence from Symphony and Codex logs for further analysis.

You cannot use this debugging workflow without a session ID or issue identifier. The Skill requires these correlation keys to trace Symphony and Codex logs and pinpoint the root cause of execution failures.

Symphony sessions get stuck during execution due to various runtime issues. This Skill traces the session lifecycle using log files and issue identifiers to classify the problem, validate scope, and identify the specific failure point.