web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Job Queue Not Executing Automatically

(7) ShareShare
ReportReport
Posted on by 56

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

 

I have the same question (2)
  • Suggested answer
    Suresh Kulla Profile Picture
    50,247 Super User 2025 Season 2 on at
    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?
     
  • Sanchith Fernando Profile Picture
    56 on at
    I'm using BC SaaS and notice only for customized job queues
  • Suggested answer
    Sumit Singh Profile Picture
    10,299 on at
    Hi Sanchith, 
     

    May be causes of not running automatically:-

    1. 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.
    2. 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.
    3. 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.
    4. 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).
    5. 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.
    Please mark “Verified” if it helps.
     
  • Suggested answer
    YUN ZHU Profile Picture
    95,748 Super User 2025 Season 2 on at
    It looks like the Starting Time is not set. You can try this first.
     
    Hope this helps.
    Thanks.
    ZHU
  • Suggested answer
    Rishabh Kanaskar Profile Picture
    6,150 on at
    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
  • Suggested answer
    Pallavi Phade Profile Picture
    4,141 on at
     
     
    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 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,066

#2
YUN ZHU Profile Picture

YUN ZHU 658 Super User 2025 Season 2

#3
Sumit Singh Profile Picture

Sumit Singh 595

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans