Why a scheduled job did not run

The optional cronjob plugin must be installed and enabled, and your account must have access to it. If Automation is missing, ask your administrator to check the plugin and your access. Use the job history to distinguish a run that was skipped from one that failed or whose result could not be delivered. The history records an outcome and, when available, a result preview. A one-time wake-up is consumed when it runs; recurring jobs remain scheduled unless you pause or remove them.

Check the run history

1. Open Automation.
2. Go to History and find the job by name or expected time.
3. Select the run to inspect its state, timestamps and result. If the full result is unavailable, use the preview shown in the run details.

No entry at the expected time may mean the schedule is paused, the due time has not arrived in the scheduler's time zone, or the scheduler was unavailable. Daily and weekly work can run later on the same due day after downtime; a missed weekly day is not replayed.

Read the outcome

A skipped run did not start a model response. A configured check that fails or prints nothing skips the run; an unavailable project or a permission change can also prevent execution. A failed run means the scheduled turn returned an error. A successful run whose result did not arrive in its conversation is a delivery problem, not a missing execution; the owner receives an alert and can find the result in history.

Fix and verify

1. Check that the job is enabled and its schedule and time zone are what you intended.
2. Read the run details for a skipped reason or error. For a check, verify the command works in its configured execution environment and produces output.
3. If the job uses a managed project, confirm it is still available and accessible.
4. Correct the job or its access, then use Run now for a recurring job when you want to test immediately.
5. Return to History and confirm the new outcome and result.

For schedule semantics and permissions, see Scheduling.