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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Job Queue (CU 250) stuck
Small and medium business | Business Central, N...
Suggested Answer

Job Queue (CU 250) stuck

(4) ShareShare
ReportReport
Posted on by Ttobi 23

Hi, 

 

I've got an issue for one of our customers (SAAS).

We are encountering a strange issue where a job queue keeps hanging and is blocking other queues.

The codeunit which is causing the issue is the CU 250 Gen. Jnl.-Post via Job Queue.

The journals get posted with background posting which creates the job queue entries. 

On regularly basis one of the entries gets stuck, doesn’t get marked as error and prevents the other jobs (CU250) to run. 

The problem only can get resolved when setting the queue to error. 

We’ve analyzed this and figured out that the related journal couldn’t be posted due to an error (e.g. missing posting setup for the posting groups). 

Does anyone had the same issue? 

Looking forward to your response.

 

Thank you, 

 

Tobias

Categories:
Dynamics 365 Business Central
  • Suggested answer
    Alex A Profile Picture
    Alex A 3,200 Super User 2026 Season 1 on at

    Yeah I mean the Job Queue can get stopped for the same reasons a user can get stopped. Insufficient permissions, out of range posting dates, missing posting setups.

     

    Finish your posting setup, and make sure that the account the Job Queue runs under has the proper setup and permissions.

     

    Other than that, please elaborate more. What is the error left in the Job Queue Log? Is this related to a customization?

  • Suggested answer
    YUN ZHU Profile Picture
    YUN ZHU 103,635 Super User 2026 Season 2 on at

    Could the issue be caused by running it too frequently? Please try setting it to run once per day. Additionally, you can try running it manually from the UI to see if any errors are triggered.

     

    Thanks.

    ZHU

  • Ttobi Profile Picture
    Ttobi 23 on at

    Hi @Alex A ,

    thank you for the quick reply. 
    The main issue is, that the job queue doesn't show an error and is stuck being on proessing, which causes other job queues to wait until this is resolved by hand. 
    As the customer has a high volume of orders, postings etc. they have to rely on the system running smooth. 
     

    There can always be issues like no valid posting date etc. which still should throw an error in the job queue. 
    This happens most of the times too, but some entries just get stuck. 

    All the users have the correct permissions and it happens to different users as well. 

    As mentioned we are just using the background posting standard functionality which uses CU 250. 

    Warm regards,

    Tobias

  • Ttobi Profile Picture
    Ttobi 23 on at

    Hi @YUN ZHU 

    thank you for the quick reply. 

     

    As stated in my previous post we are using standard backgroud posting where BC should organize the posting via Job Queues itself. We don't have any customizations added to this process. 

     

    The jobs are set up to run once.
    But they are actually creating a lot of backgroud posting jobs at the same time. But still BC should be able to process all of them. 

    Running it by hand will throw the expected error. When resetting the job queue it will be processed correctly. But right now the customer can't rely on the process which causes extra work for the customer.


     

    Warm regards,

    Tobias

  • Suggested answer
    AndrewThomas81 Profile Picture
    AndrewThomas81 3,009 Super User 2026 Season 2 on at

    Have you checked the job queue log entries for further information on why it is failing?

     

    Kind Regards

     

    Andrew Thomas FCCA MCP

    YouTube - Use Business Central

    LinkedIn

  • Suggested answer
    OussamaSabbouh Profile Picture
    OussamaSabbouh 20,100 Super User 2026 Season 2 on at

    Hello Tobias,

    What you are seeing is not the expected Job Queue behavior. Microsoft documents that when a job running in the background throws a posting exception, the Job Queue Error Handler should move the entry from In Process to Error and store the error in Job Queue Log Entries; because general-journal background posting uses a common Job Queue Category, one entry that remains incorrectly stuck in In Process will also block subsequent CU 250 entries in that category, which explains your symptom. Since you have confirmed that the journal itself contains a normal posting error such as missing posting setup, I would reproduce it in a sandbox and check Job Queue Log Entries → Copy Details plus Application Insights: look for the job-start event AL0000E25 and whether you subsequently get failure event AL0000HE7 / completion AL0000E26. If CU 250 starts but neither the normal failure handling nor completion occurs, this points to a background-session/platform or Microsoft application issue rather than the journal posting error itself, and for SaaS I would open a Microsoft support ticket with the Job Queue Entry ID, timestamp/time zone, AL stack trace, and telemetry. Manually setting the entry to Error is a reasonable temporary recovery, but Maximum No. of Attempts will not solve an entry that never leaves In Process. As a temporary operational workaround, you could also disable background posting for general journals until the root cause is resolved.

    Regards,
    Oussama Sabbouh

  • Ttobi Profile Picture
    Ttobi 23 on at

    Hi @AndrewThomas81 ,

    sadly there are not job queue log entries which failed. It is still being in process.

  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    Grigorios Mavrogeorgis 3,638 Super User 2026 Season 2 on at

    Hi Tobias, I seen something similar and in that case it was not the posting error itself, it was something asking for user input inside the background session. Normally a plain error like missing posting setup just puts the entry in Error. If the entry stays In Process, most likely something tries to show a Confirm, a page or a message, there's nobody to answer, and it waits until the timeout. Since all CU250 entries share the same job queue category, everything behind it waits too.

    I'd check the installed extensions first, especially anything subscribing to journal posting events that calls Confirm or Page.Run without checking GuiAllowed. Telemetry on the job queue lifecycle should show you where it stops. If you can reproduce it in a sandbox with the same journal, even better.

    Meanwhile, as far as I know there's a timeout field on the job queue entry, lower it so a stuck entry fails faster. And turn on Background Error Check on the journal batches, so missing setups are caught before posting.

    Glad to help - follow up if anything is unclear.
    ► If this solved it, marking it verified helps others too.
    Regards,
    Grigorios Mavrogeorgis
    Business Central Consultant & AL Developer
    Work: Gmsoft Limited
    Blog: insidebusinesscentral
    LinkedIn: linkedin.com/in/gregorymavrogeorgis

  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    Grigorios Mavrogeorgis 3,638 Super User 2026 Season 2 on at

    Hi Tobias, the blocking part is by design I think. Background posting usually runs with a Job Queue Category from General Ledger Setup, and in a category only one runs at a time, the rest wait until it finishes. So one entry stuck In Process holds the whole line.

    The real question is why it stays In Process. Normally a posting error like missing posting setup flips the entry to Error and you see it in Job Queue Status on the journal. When it doesn't, from what I've seen the background session ended without the error handling finishing, so nobody updated the entry. Why here, I can't say. I'd check Job Queue Log Entries and Scheduled Tasks for that entry, and the job queue signals in telemetry if you have Application Insights connected.

    To reduce it meanwhile, turn on Background Error Check on the journal batch, so the missing setup shows up before the user posts.

     

    Glad to help - follow up if anything is unclear.   

    ►  If this solved it, marking it verified helps others too.       

    Regards,
    Grigorios Mavrogeorgis
    Business Central Consultant & AL Developer

    Work: Gmsoft Limited
    Blog:  insidebusinesscentral
    LinkedIn: linkedin.com/in/gregorymavrogeorgis

  • Suggested answer
    D365BC_AmanKr Profile Picture
    D365BC_AmanKr 180 on at

    Hi Tobias,

    The key point is that the journal posting error itself should normally be handled by the Job Queue framework; it should not leave CU 250 permanently in In Process. Since the journal has a legitimate error such as missing posting setup, first correct the posting configuration and test the same scenario manually. If CU 250 still remains stuck without changing to Error, investigate the background session rather than the journal itself. Check the Job Queue Log Entries, session/activity details, and telemetry to determine whether the job started but never reached either the failure or completion stage. If reproducible in SaaS, capture the Job Queue Entry ID, execution time, environment, and error/telemetry details and raise it with Microsoft Support. Setting the entry to Error is an appropriate temporary recovery, but the underlying cause should be investigated if the behavior continues.

    Hope it will help you.
    Please Verify if you found the answer helpful so that it will help others.

    Many Thanks
    Aman 
     

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 750 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 534 Super User 2026 Season 2

#3
AndrewThomas81 Profile Picture

AndrewThomas81 287 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans