Share
ReportWe’re currently in the process of migrating from NAV to Business Central SaaS (not in production yet) and have recently run into what appears to be a Job Queue / Scheduled Task dispatcher issue affecting our environments.
We are currently running on Business Central 27.2 and have not updated the environment in months. Prior to approximately 5/14/2026, everything had been operating normally and Job Queue processing was generally very fast/responsive.
Starting around 5/14/2026 (possibly slightly earlier), we began seeing severe delays between Job Queue enqueue and actual start time. In many cases:
- Jobs enqueue immediately (
AL0000E24) - But do not actually start (
AL0000E25) for 10–75+ minutes - Once they DO start, they complete very quickly (typically 1–5 seconds)
A few additional observations:
- Standard API/OData calls to BC are fast and responsive
- Actual webhook/API execution time is fast
- Queue depth appears relatively low
- We are seeing large delays specifically in scheduled task/job queue dispatch
- Standard Microsoft jobs like
RC Headlines Executor(Codeunit 1441) are also delayed, which makes this seem broader than our custom integrations
Telemetry findings from Application Insights:
API Webhook Notification Sendjobs are heavily impacted- We are seeing scheduler orchestration events like:
AL0000P9F(Job queue entry rescheduled as waiting)AL0000P9G(Next waiting job queue entry activated)AL0000KZV(Job queue entry task cancelled)
We’ve already tried:
- Putting all jobs On Hold
- Clearing Scheduled Tasks
- Recycling the Sandbox environment
- Reducing/disabling integration polling jobs
- Disabling custom code
- Reviewing SQL/API telemetry
We also tested this behavior in:
- Production
- Multiple workspaces/environments
…and we are seeing the same symptoms there as well.
One thing that loosely resembles this behavior is Microsoft Issue ID 6385109, though our symptoms don’t match it exactly.
Our vendor has opened a ticket with Microsoft and we are currently awaiting a response, but I wanted to see if anyone else in the community has experienced anything similar.
At this point, this is becoming a major concern for our go-live. The issue has now been occurring for 5+ days and would impact multiple production processes that rely heavily on the Job Queue and Scheduled Task framework.
Has anyone else seen:
- long enqueue → start delays in BC SaaS?
- scheduler/session dispatch latency?
Job Queue Dispatcher/Job Queue Start Sessiontasks lingering in READY state?- webhook notification backlog despite fast execution runtimes?
Would especially appreciate insight from anyone who has seen similar scheduler/background-session issues in SaaS.
Thanks!
All responses (
Answers (
1,909
