When a schedule is not running, check mate leave, paused jobs and the host time zone first. Then distinguish one failed job from a scheduler-wide problem.

Open the dashboard → Management → select a mate → Schedule. Read each row’s last and next times and any page warning.

First checks

Check the selected mate and her status. Wake her if she is stopped or on leave and should resume work.
For Paused, select Resume when the work should continue.
Compare system time with the next run. Schedules use the host’s time zone. New jobs begin at the next scheduled time.
For change-monitoring jobs, distinguish a URL check from work triggered by a change. An unchanged page may produce no new result.

A scheduled-work load error means data is unavailable, not that no jobs exist.

One job keeps failing

For Last run failed or repeated failures, select Pause to stop repeated work and credit use.
Read the failure reason. Check models and authorisation, task instructions, data and tool permissions.
If instructions need changing, follow Schedules. Keep the existing setup before changing it.
Check that the task is safe to run immediately, then select Run now once. This executes real work and may use AI credit, send notifications or perform the assigned action.
After Finished running., inspect the result and destination. For a failed run, read the reason below. Resume the schedule after fixing and confirming it.

No jobs run

This mate’s scheduler has stalled — no scheduled work will run. or a notice that nothing has completed for a long time requires a broader check.

Check leave, models and host resources first. If a restart is needed, follow Mate controls, wait for recovery and recheck Schedule. Once the warning clears, verify with one low-impact job.

Still failing?

Stop repeated execution and contact support with the mate, job name, host time zone, expected and actual times and the warning or run record. Some jobs produce chat or notifications rather than a report; check their configured destination.

scheduled job cron scheduler failed automation no execution