Job Queue not running every 1 minute in Business Central

(4) Share

Report

Posted on by Mahek Mehta

288

Hi everyone, I have configured a Job Queue Entry to run every 1 minute in Business Central.

Settings:
- Recurring Job = Enabled
- Run on all days (Monday–Sunday)
- No. of Minutes between Runs = 1
- Status = Ready

However, the job does not run every minute. In Job Queue Log Entries, I see that it runs every 5 minutes instead.

The job is Codeunit 5339 – Integration Synch. Job Runner.

Is there any server configuration or limitation that prevents jobs from running every minute?

Has anyone faced this issue before?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (1)

Sort by

AndrewThomas81 558 on at

Like (0)

Report
Copy link

Link copied!

Form the job queue log entries, how long does it take to run?

Was this reply helpful? Yes No
Verified answer

YUN ZHU 99,740 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

The Job Queue is not designed to run every minute; please refer to the documentation below.

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-job-queue?wt.mc_id=DX-MVP-5004336#job-queues-and-performance

For real-time synchronization, please use Power Automate or the API.

PS:

Can we timely synchronize Dataverse entity changes without Power Automate? Yes, but……

Using OAuth 2.0 to connect Dataverse tables (APIs) in Postman (Using Grant type: Client Credentials, not Implicit) – Get, Patch, Post and Delete

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Levi B 24 on at

Like (0)

Report
Copy link

Link copied!

You absolutely can run a job queue every minute, however the Integration Synch. Job Runner, sets the job queue status to On Hold Due to Inactivity when it doesn't find any changes in the table. This causes the entry to wait for the duration of the Inactivity Timeout field, which you already have set to the minimum of 5 minutes. Most likely the job is not finding any changes when running, causing it to only re-run every 5 minutes.

See documentation: https://learn.microsoft.com/en-nz/dynamics365/business-central/admin-scheduled-synchronization-using-the-synchronization-job-queue-entries#about-inactivity-timeouts

If you don't want to wait for the inactivity timeout you would likely need to wrap the sync function in a custom codeunit.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 14,089 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

This behavior is expected because the job is currently “On Hold with Inactivity Timeout” and the Inactivity Timeout Period is set to 5 minutes, so even if the recurrence is set to 1 minute, Business Central will pause the job when no activity is detected and only wake it up after the inactivity period (5 minutes). This is typical for synchronization jobs like Codeunit 5339 – Integration Synch. Job Runner, where BC optimizes execution by not running continuously when there are no changes, so the job effectively runs every 5 minutes instead of every minute.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No