Loading

Scheduled Apex Jobs Remain in Queued Status on the Apex Jobs Page

Publish Date: Jun 2, 2026
Description

Scheduled Apex jobs in Salesforce remain in Queued status on the Apex Jobs page even after they have executed, which can cause confusion for administrators expecting the status to change after execution. This article explains why scheduled jobs retain Queued status by design, the difference between the Apex Jobs page and the Scheduled Jobs page, and how to properly abort or delete scheduled jobs.

Resolution

Scheduled Apex jobs are designed to remain in Queued status until their NextFireTime is set to null — meaning no future scheduled execution remains. This behavior is intentional and does not indicate the job is stuck or failing.

How Job Status Works

Scheduled jobs appear on both the Apex Jobs page and the Scheduled Jobs page. On the Apex Jobs page, the status displays as Queued. When the job has no future NextFireTime, the AsyncApexJob record is marked Completed. If the job is aborted, the AsyncApexJob row is marked Aborted.

Recurring vs. One-Time Scheduled Jobs

A job that recurs indefinitely will never be marked Completed on the Apex Jobs page. It will only be marked Completed if the execute() method sets the NextFireTime to null after the last execution. One-time jobs that have no further scheduled execution will eventually show as Completed.

How to Abort or Delete Scheduled Jobs

Scheduled jobs cannot be aborted from the Apex Jobs page. Use the Scheduled Jobs page in Setup to manage, pause, or delete scheduled jobs.

Execution Limit Note

Even though a scheduled job appears on both the Apex Jobs and Scheduled Jobs pages, it counts only once against the asynchronous Apex execution limit.

Additional Resources

Monitor the Apex Job Queue

Knowledge Article Number

000383866

 
Loading
Salesforce Help | Article