Troubleshooting Scheduled Task or Cron Job Does Not Run
A scheduled job or task does not appear to run at the expected time.
Apps and Packages both medium severity
Symptom A scheduled job or task does not appear to run at the expected time.
What this usually means Use this when scheduled automation never starts or behaves as if it never ran, and you need to inspect schedule, identity, environment, and logs.
Meaning of the symptom
When scheduled work does not run, the safest assumption is that the scheduler context differs from your manual testing context.
Safe sequence
- Confirm the schedule and expected time.
- Check scheduler history or logs.
- Compare scheduler context with your manual run.
- Fix one context assumption and retest.
Common branch decisions
- If there is no run attempt, focus on schedule definition and enablement.
- If there is a run attempt with failure, focus on environment, path, or permissions.
- If it runs but produces nothing, inspect output path and variables next.
First checks - Confirm the schedule syntax and the expected local time.
- Check whether the task history or cron logs show any execution attempt.
- Verify which account the scheduler uses.
Common causes - Bad schedule expression or wrong time assumption.
- The task exists, but the account, shell, or working directory is wrong.
- The script fails immediately and no one is checking scheduler logs.
What not to do - Do not wait for the next run without checking logs or history.
- Do not assume the scheduler uses the same environment as your terminal.
- Do not duplicate jobs until you know why the first one failed.
Recovery steps - Check scheduler history, cron logs, or task result codes.
- Run the exact command under the scheduler's account or context if possible.
- Fix schedule, working directory, or environment assumptions, then retest.
How to verify the fix - The job runs at the expected time or on a safe test trigger.
- Expected output appears in the right location.
- You can explain whether the problem was schedule, identity, environment, or script failure.
Related reference Related visuals and reference support will appear here as this area expands.