We have a job queue that runs report 296 Sales Order Post Batch. It runs three time a day, but after the latest update to BC Cloud version 25.2.27733.28869 it stop working. I'm not sure if it's related to the update. I have also tried to run the post batch from Sales Order List. It runs the report but nothing happens. I have set the right filters.
If you cannot find a clear source of the problem, you may need to generate a ticket to the MS support area. I remember once having problems with project queues not executing and it was an internal problem.
I also faced the same problem and I am searching for a solution on the internet and I am glad that I found your post where I found my answer.When I was searching for this on the internet I also found a link to the guest post service https://linkinpaws.com/.They helped to promote my blog: now I know where to turn to in order to raise the site to the first positions in the search results.
1. Go to the Job Queue Entries and review the error messages or logs for the batch job. This might give a clue about why it's failing.
2. Ensure that the user running the job has sufficient permissions for posting sales orders. Sometimes updates alter permission requirements.
3. Double-check your filters in the Job Queue Entry and the report itself. Even minor discrepancies in the filter setup could stop the process.
4. Try running Report 296 directly from the Sales Order List without the job queue. If it doesn’t work, this confirms the issue isn’t limited to the job queue but lies in the report or system logic itself.
If you have access to a developer, you can use the Start Debugging tool in BC to trace what happens when the report runs. This can reveal if any code modifications or extensions are interfering.
Review any installed extensions that might be interacting with the sales posting process. Temporarily disabling them could help identify conflicts.
This should help
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.