Debug failed schedule runs

Diagnose from evidence before changing cadence, retries, or credentials.

Prerequisites

• Obtain the schedule ID from the user or the schedule list.
• Define the incident window and the expected endpoint behavior.
• Do not ask the user to paste secret header values or full tokens.

Workflow

1. Read the current schedule configuration with get_schedule.
2. Read the latest history page with get_schedule_history.
3. Compare several runs to identify a persistent error or a one-off event.
4. Classify the failure before proposing a bounded fix.
5. Verify the next run or a separately authorized test after a change.

MCP examples