Scheduled Jobs Troubleshooting
Symptom-by-symptom resolutions for the most common Scheduled Job issues.
Understanding the Status Field
The Status column on the Scheduled Jobs list is the fastest way to diagnose what a job is doing. Possible values:
| Status | What It Means |
|---|
| Idle | The job is not currently running. This is the normal at-rest state; the job will pick up at its next scheduled fire. |
| Pending | The job has been selected by the dispatcher and is about to run. In a healthy portal this state lasts a few seconds; if a job sits in Pending for more than a couple of minutes, the dispatch was interrupted — see below. |
| Processing | The job is currently running. It will return to Idle when it finishes. |
| Error | The last run threw an exception before completing. Details are in Setup > Manage > Event Logs. The job will still be picked up on its next scheduled fire. |
| Failed | The dispatcher was unable to invoke the job at all (routing/permissions problem, controller not found). Details are in Setup > Manage > Event Logs. |
Common Symptoms and Resolutions
| Symptom | Likely Cause | Resolution |
|---|
| Job is Enabled and its Interval has elapsed but Last Fire Time never updates. | Starts On is in the future, or Ends On is in the past. | Open the job and verify Starts On is at or before the current UTC time and Ends On (if set) is in the future. |
| Job is stuck in Pending for several minutes. | The dispatch call did not land — usually a transient IIS or network issue. | The platform automatically resets any job that has been Pending for more than two minutes. Wait one to two minutes and refresh the list. If the job stays Pending, restart the site's application pool. |
| Job is stuck in Processing and does not complete. | The job's work is genuinely long-running (multi-day integrations do exist), or the app pool crashed mid-run. | Processing rows are not automatically time-limited — that is deliberate, because some integration syncs (particularly Salesforce full syncs) take many hours. If you know the job is stuck, an app-pool recycle will reset it: the platform auto-resets any Processing row whose last update predates the current app-pool start. |
| Job Status is Error. | The last run threw an exception during execution. | Open Setup > Manage > Event Logs and filter to the job's Last Fire Time. The exception details identify the cause. Fix the underlying issue (permission, data, integration credentials) and either wait for the next scheduled run or click More Actions > Run Now from the job's detail page. |
| Job Status is Failed. | The Action URL does not resolve to a valid controller/action, or the controller returned a non-success response before executing. | Confirm the Action URL exists on your portal. Test the URL manually if possible. Check the Event Log for the specific routing error. |
| Job appears to fire "successfully" but nothing changed. | The Action URL returned a non-2xx response, but the dispatcher recorded the job as complete anyway. | The dispatcher runs jobs fire-and-forget — it does not fail the job on non-2xx responses. Non-success responses are recorded as Information entries in the Event Log. Search the Event Log for the job's Last Fire Time to see what the target action returned. |
| Multiple similar jobs suddenly appeared on the list. | A related feature created them (Scheduled Reports auto-creates one job per active frequency; integration setup creates sync jobs; the AI Assistant creates embedding jobs). | Normal. See Standard Scheduled Jobs for the list of auto-created jobs. Do not delete them — the source feature relies on them. |
| A job runs at the wrong time of day. | Starts On was entered in local time rather than UTC. | Convert your intended local time to UTC and update Starts On. All Scheduled Job timestamps are UTC. |
| A one-time job is still on the list after running. | Auto Delete was not enabled when the job was created. | Open the job, check Auto Delete, save. Note: the Auto Delete field must be added via Edit Layout to appear on the Cron Job New/Edit form. It will remove itself after its next successful run. To delete immediately, click Delete, a standalone button located next to Edit. |
| Two Scheduled Jobs seem to be running at exactly the same time and one interferes with the other. | The dispatcher runs up to six jobs concurrently per polling cycle. Distinct jobs do run in parallel by design. | If two jobs must not overlap, combine their work into a single Action URL, or stagger their Starts On and Interval so they do not become due at the same time. |
| A previously-shipped standard job is missing from the list. | It was deleted at some point. | Contact Magentrix support to have the standard job restored. Standard jobs cannot be recreated by administrators from Setup. |
| A job with Status Error or Failed and Enabled checked gets retried far more often than its configured Interval (for example, every ~1 minute even with a 1440-minute Interval), and its Modified By / Last Fire Time keeps changing. | This is expected dispatcher behavior: jobs left in Error or Failed status while Enabled are retried on a short cycle, independent of Interval, until they succeed or are disabled. | Fix the underlying Action URL or permissions issue, or disable/delete the job to stop the rapid retries. Because the record is being updated so frequently, expect “This record has been updated since you last viewed it” conflicts if you try to edit it — reload the page immediately before editing. |
Where to Look for Details
- Event Log — Setup > Manage > Event Logs. Every failure, warning, and non-2xx job response ends up here with the job's ID and timestamp.
- Sync History — for integration jobs (Salesforce, Dynamics, HubSpot), a Sync History entity records each sync run with its status and note. Open the integration's sync job to see linked Sync History entries.
- Scheduled Report state — for report-run jobs, each Scheduled Report record carries a Last Run Date and Last Run Result (Success / Error / Warning). Inspect the report record itself for run-level detail.
When to Contact Magentrix Support
Open a support case if:
- A shipped standard job is missing and you need it restored.
- A job stays in Processing indefinitely and app-pool recycling does not reset it.
- Event Log entries reference internal errors that are not resolvable from Setup.
Include the job's Job Number, its Last Fire Time, its Status, and the relevant Event Log entries (ID and timestamp) when opening the case.
<< Configuring Scheduled Jobs