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

Problem with understanding job que next run

(6) Share

Report

Posted on by AntonioKD

432

Hello,

I have a problem with my job que.
It is set as a recurring job and I want to run it everyday at 11 pm (23:00).
And I have this job que set lik this:

But the problem is that it was run on 22/07/2025 at 11 pm (23:00) lasted more than 1 hour, so ended at the next day and next run is 24/07/2025 at 11 pm (23:00) - 23/07/2025 is missing. Why is that working like that? Could you explain me how this time of the next run works? How should I set this job que to be sure that it will run everyday at 11 pm? No matter how much time it takes to end this function?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Matteo Fiocco 260 on at

Like (2)

Report
Copy link

Link copied!

Hi! This happens because your job started at 23:00 and ended after midnight (around 00:26). Business Central considers the job as already executed for 23/07, so it skips that day.

To make sure it runs every day at 23:00, regardless of how long it takes:

Create two job entries: one for even days, one for odd days.

This avoids the overlap issue and ensures daily execution.

Let me know if you need help setting that up!

Was this reply helpful? Yes No
Rakolup 8 on at

Like (3)

Report
Copy link

Link copied!

It looks like you’ve set the job queue to run at 11 PM (23:00), but since it’s a recurring job, you need to ensure that the recurrence is properly set for every day. Make sure the “Recurring Job” option is turned on, and also check the days you want it property management to run. You’ll need to activate the days for it to run daily.
Also, make sure the "Ending Time" is set correctly, or leave it blank if you want it to run continuously. If it’s still not running as expected, double-check for any conflicting settings or the system time.

Was this reply helpful? Yes No
AntonioKD 432 on at

Like (2)

Report
Copy link

Link copied!

Something is wrong because I have my job que run on 10 pm that last 1H 6min and still is missing one day:

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,173 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!
Why the Job Didn't Run on 23/07/2025

The job is scheduled to run daily at 23:00, but:

On 22/07/2025 at 23:00, it started as expected, but ran into the next day (past midnight).

Your job has Starting Time = 23:00 and Ending Time = 23:00 (same time).

That means the valid window to start the job is exactly between 23:00 and 23:00 (i.e., only 23:00 sharp, not after midnight).

Since the job from 22nd was still running when 23rd came, the system skipped the 23rd run because:

A job cannot start again until the previous run has ended.

The 23:00 window had passed by the time the previous job finished (it was outside the defined window).

✅ How to Fix This: Let the Job Start Anytime After 23:00

To ensure the job runs every day at 23:00, no matter how long the previous one took, update the time window:

✅ Recommended Setup:

Starting Time: 23:00:00

Ending Time: 23:59:59 (or 00:00:00 to allow start after midnight)

No. of Minutes between Runs: Leave blank or 1440 if daily

Job Timeout: Leave as is (12 hours is fine)

Ensure Recurring Job is enabled

Continuous Job: Leave disabled unless needed

This allows Business Central to start the job at 23:00 or shortly after, even if the previous job ran long.

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 9,116 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
Hi Antonio,

It’s a common point of confusion when a recurring job queue entry runs longer than expected and ends up skipping the next scheduled run.

Here’s what’s happening:

When a job queue entry is marked as Recurring and set to run every 1440 minutes (i.e., once per day), BC calculates the Earliest Start Date/Time for the next run based on the completion time of the previous run — not the original scheduled time. So if your job started on 22/07/2025 at 23:00 and finished at 00:26 on 23/07/2025, the system adds 1440 minutes to that end time, resulting in the next run being scheduled for 24/07/2025 at 23:00.

To ensure the job runs every day at exactly 23:00, regardless of how long it takes, you’ll want to:

Clear the No. of Minutes between Runs field

Set the Starting Time to 23:00:00

Tick the Recurring Job checkbox

Leave the Ending Time blank (unless you want to restrict the window)

Use the day-of-week checkboxes to select all days (Mon–Sun)

This setup tells BC to evaluate the job daily at 23:00, rather than calculating the next run based on the previous job’s end time. It’s a cleaner recurrence model for time-fixed jobs.

Helpful References:
Schedule jobs to run automatically – Microsoft Learn
The Job Queue Guide – BC Geek
Community Thread on Next Run Date Formula
Run Job Queue via AL – Dynamics 365 Lab
Job Queue Management Deep Dive – Dynasol

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No
Suggested answer

CU26110717-0 10 on at

Like (1)

Report
Copy link

Link copied!

This issue happens because the scheduler calculates the next run based on the scheduled time, not when the job finishes.

When your job crossed midnight, the system skipped the next day since overlapping runs aren’t allowed.

Set your cron to run daily at 11 PM and enable overlapping/multiple executions.

This ensures it will run every day, no matter how long the previous job takes.

Also, if you love trying US favourite foods like Dave’s Hot Chicken, it’s worth checking out.

Was this reply helpful? Yes No