Current Configuration in Microsoft Dynamics 365 Business Central:

The Job Queue functionality currently calculates the next run date for recurring jobs based on the completion time of the previous run. As a result, if a job scheduled for 11:00 PM completes after midnight (e.g., 12:05 AM), the base date becomes the next day, and adding (for exp: 1D) pushes the next run to the day after tomorrow. This behavior is by design.

Limitation Faced by Customers:

Customers who require jobs to run at a fixed time every day (e.g., 11:00 PM daily) encounter an issue when jobs finish after midnight. Instead of scheduling the next run for the following day at the same time, the system skips a day. For example:

• Scheduled time: January 16th, 11:00 PM
• Job finishes: January 17th, 12:05 AM
• Next run calculated: January 18th, 11:00 PM (skips January 17th) This creates operational challenges for businesses that rely on consistent daily execution, such as end-of-day processes, data synchronization, or integrations.

Customer Proposal for Improvement

Users cannot predict when a job queue will run past midnight, and having to check and manually edit the schedule every day defeats the purpose of an automated recurring job queue. This creates unnecessary overhead and negatively impacts customer experience. Therefore, we propose an enhancement to the Job Queue logic that allows fixed-time recurrence independent of the completion time. Microsoft should provide an option to ensure that the next run is scheduled for the configured time (e.g., 11:00 PM) on the next calendar day, regardless of when the previous job finished.