Small and medium business | Business Central, N...

Job Queue Not Executing Automatically

(9) Share

Report

Posted on by Sanchith Fernando

Hello Team,

I am experiencing an issue with the job queue not running automatically.

The job queue status is set to Ready.

I set the Earliest Start Date/Time to a future time (two minutes ahead of the current time).

The No. of Minutes between Runs is set to 1.

However, the job does not execute after the expected time has passed, and the Earliest Start Date/Time does not update. The queue remains in Ready status with no errors displayed.

When I use the Run Once (Foreground) action, the job runs successfully without any issues. I also tried deleting and recreating the job queue, but the issue persists.

Could you please advise why the job queue is not running automatically and how this can be resolved?

Thank you,
Sanchith

Categories:

Dynamics 365 Business Central

I have the same question (3)

All responses (7)

Answers (0)

Suggested answer

Suresh Kulla 50,255 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Are you using BC SaaS or BC On-Prem?

Check the Task Scheduler Settings if you are using OnPrem, and if not, is this happening on every job or only a specific job?

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/configure-server-instance#Task

1 people found this reply helpful.

Was this reply helpful? Yes No
Sanchith Fernando 60 on at

Like (2)

Report
Copy link

Link copied!

I'm using BC SaaS and notice only for customized job queues

Was this reply helpful? Yes No
Suggested answer

Sumit Singh 11,382 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!
Hi Sanchith,

May be causes of not running automatically:-

Background Sessions Disabled

In Business Central Admin Center, check that Allow Background Sessions is enabled for the environment.

If disabled, no job queues will run automatically.

Job Queue Category Not Assigned

If the job queue entry uses a Job Queue Category, ensure the category is linked to the correct Background Session in the service configuration.

Earliest Start Date/Time

If this is set in the future, the job will not run until that time.

For recurring jobs, ensure Recurring Job = Yes and No. of Minutes between Runs is set.

User Session vs. Background Execution

The job runs in a background session under the service account, not the user who created it.

Ensure the service account has permissions to run the object (SUPER or equivalent).

Check for Errors in Job Queue Log Entries

Even if the status is Ready, check Job Queue Log Entries for hidden errors.

You can try below:-

Enable Allow Background Sessions in Admin Center.

Restart the Business Central service instance (for on-prem) or refresh the environment (for SaaS).

Verify the job queue entry:

Status = Ready

Recurring Job = Yes (if needed)

Object Type and Object ID are correct

Remove Earliest Start Date/Time or set it to current time.

Official Documentation:
· Schedule Jobs to Run Automatically (Job Queues)
https://learn.microsoft.com/en-us/dynamics365/business-central/admin-job-queues-schedule-tasks [Schedule j...ss Central]
· Job Queue Overview
https://learn.microsoft.com/en-us/dynamics365/business-central/srb/setup/job-queue [Job queue...soft Learn]
· Task Scheduler (How Job Queues Work in Background)
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-task-scheduler [Task sched...soft Learn]

Please mark “Verified” if it helps.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 97,429 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

It looks like the Starting Time is not set. You can try this first.

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,211 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hi,

This usually happens because the Job Queue Dispatcher is not running in the background. In BC SaaS and on-prem, the dispatcher handles automatic execution:
> Check that the Job Queue Entry is assigned to a Job Queue Category and that the Job Queue Dispatcher (background session) is running.
> In SaaS, verify the Job Queue is enabled under Job Queue Entries > Process > Start Job Queue.
> Ensure the environment’s background sessions are not disabled (Admin Center > Session Settings).
> For on-prem, confirm the BC Server service is running with Job Queue enabled in the service configuration.
> If the queue is stuck at “Ready,” try clearing out all suspended/blocked entries and restart the dispatcher.

Foreground works because it uses your session; automatic runs need the dispatcher session active. Re-enable/start the Job Queue from the page or service level to resolve.

Thanks

Rishabh

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,070 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Namaste @Sanchith Fernando

Can you check below setup in your job queue . Starting time should be present

Increase Frequency from 1 minute between two runs to 60 or more than 60 mins . In above example , i have 1440 mins it means 24 hours .

If you feel helped , Please mark as "Verified"

Regaards

Pallavi Phade

Was this reply helpful? Yes No
Pbat 20 on at

Like (0)

Report
Copy link

Link copied!

@Sanchith Fernando, Did you ever found out what happened and figured a solution?

I am experiencing the exact same problem. I've read the answers here, but I can't find any 'Allow Background Session' in the admin center. Is that applicable for BC cloud versions too?

Was this reply helpful? Yes No