workflow-debugger

Workflow debugging identifies why workflows fail by examining logs, checkpoints, and budget data to provide root-cause analysis. It helps determine if failures stem from contract violations, budget issues, or external errors.

A workflow failing mid-execution can be diagnosed by examining checkpoint states, agent logs, and budget traces. This process determines if the failure was caused by a contract violation, a budget issue, or an external error, providing clear evidence for the root cause.

Post-mortem analysis on a successful workflow inspects checkpoint states, agent logs, and budget traces to identify cost and performance optimization opportunities. This analysis yields actionable recommendations for improving future workflow orchestration efficiency.

Yes, troubleshooting workflow failures provides prioritized, actionable fix recommendations complete with effort estimates. By inspecting checkpoint states and budget traces, you receive clear instructions on how to resolve workflow orchestration issues.

The best way to troubleshoot workflow orchestration issues is by analyzing agent logs, checkpoint data, and budget traces. This approach provides root-cause analysis with evidence, distinguishing between contract violations, budget issues, and external errors.

To debug a Gorgon workflow run, you need the checkpoint database and the agent log path. Providing these inputs allows the debugger to inspect states, logs, and budget traces to generate root-cause analysis and actionable fixes.