debugging-broken-jobs

To triage broken Friday workspace jobs with empty output, call describe_session on the failing session to review the agent's tool calls. This structured triage process routes you to the dedicated empty-output debug workflow instead of unnecessary FSM rewrites.

Friday workspace job failures like runtime errors or infinite tool loops are almost always caused by agent contract violations or configuration errors. Reviewing the agent's tool calls through structured triage identifies the root cause before attributing it to platform bugs.

The best way to debug Friday workflow failures is to follow mandatory diagnostic steps that validate agent contract compliance. This structured triage approach eliminates misdiagnosis of FSM wiring issues by confirming configuration errors before escalating platform bug claims.

Yes, structured triage applies to all Friday workspace job failure scenarios including incorrect job invocations. By mapping job failure signatures to specialized debug skills, it enforces pre-escalation checks to validate agent contracts and route you to the correct resolution workflow.

Yes, you must validate agent contract compliance before reporting a Friday workspace job failure as a platform bug. Mandatory diagnostic steps enforce pre-escalation checks to prevent false platform bug claims caused by configuration errors or contract violations.

If your Friday workspace job is not working despite correct FSM wiring, use structured triage to map the job failure signature to a specialized debug skill. This enforces checking agent contracts and configuration errors before attributing the failure to the platform.