Cron Incident Triage

A historical cron inventory is a starting point, not proof that a command is currently scheduled. Identify the exact job, environment and expected outcome with its owner.

1. Check the most recent known execution and whether it produced the expected local result and downstream handoff.
2. Investigate the relevant error, cursor or lock using the workflow's source-backed documentation. A lock, an advanced cursor or a provider timeout may require different recovery steps.
3. Confirm the destination state and the job's duplicate/retry behavior before proposing a replay.
4. Agree on a targeted recovery and verify the result with the responsible owner.

Production diagnostics require approval for the exact command and target. Stopping a process, changing a lock or data, and restarting a job are separate actions requiring authorization; this page does not provide a generic restart recipe. For orders, start with Sales import.