Skip to main content

A scheduled job didn't run when I expected

Why a scheduled job runs late, or not at all, and what to check.

Symptom​

A scheduled job's History shows no run at the time you set, or the run came later than its schedule.

Find the cause​

  1. Open the Scheduled Jobs tab and check that the job is on.
  2. Open the job's History.
    • If there's a failed run at about the right time, go to The run failed.
    • If there's an entry that starts Scheduled job skipped:, go to The schedule can't be read.
    • If there's nothing, read the causes in order.

The job is off​

Cause: Jobs that are off don't run.

Solution: Turn the job on in the Scheduled Jobs list.

It isn't late yet​

Cause: Script Master checks for due jobs once an hour, so a job can start up to an hour after its time. A job set to run more often than once an hour still runs once an hour.

Solution: Wait for the next hourly check. To run a job right away, select Run in its row's menu in the list.

The schedule is in UTC​

Cause: Schedules run in UTC, not in your time zone. Next at: in the job's editor shows the next run in UTC.

Solution: Convert the time you want to UTC and change the schedule.

The job is new​

Cause: A new job doesn't run for a time that passed before you saved it. It runs from its next scheduled time on.

Solution: Wait for the next scheduled time, or select Run to run it right away.

The schedule can't be read​

Cause: The job's schedule isn't a valid cron expression, so Script Master skipped it. The History entry says why.

Solution: Correct the schedule in the job's editor and select Save.

The run failed​

Cause: The job ran, but its script failed, or couldn't reach the Companion App.

Solution: Open the run in History and read its error. If it says Local script execution is not supported., see Server-side modules show "Action Required".

  • Scheduled Jobs: schedules and running a job now.
  • Limits: when jobs start, and how long they can run.