Announcements
No record found.
Hello, the batch job to completely reset the Entity Store has been getting stuck in the executing state a few times. Those times the cubes won't update until someone sets the state of the job to "cancelling" manually. Why does this happen and how can we solve this? If there is no direct solution to this problem we would be happy with a custom alert that triggers when the batch job has been in the executing state for too long. Is it possible to create this in an on-premises environment with onboard methods? Thank You for your help, Jakob
I'd log a Microsoft support ticket. I've seen numerous cases of issues with the Full reset batch job and Microsoft support has been required for resolution in every case. The job seems somewhat unstable.
Hi Jakob,
Since we are talking about an On-premises implementation ( LBD = Local Business Data) Please open a support request with us.
You can use my name to get the case assigned to me if you are working EMEA hours.
Thanks,
AlexG
Hi Jacob,
There are some standard batch jobs in D365FO (e.g. Data cache refresh batch) that mostly have "Executing" status and this is misleading that if the batch job is working. especially when the batch job start date
start date is a few days in the past but that is basically when the batch service has last restarted and since then the job has executed continuously – which can be by design.
You can raise a support ticket to get a clarification from Microsoft.
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.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 617
André Arnaud de Cal... 461 Super User 2026 Season 1
Syed Haris Shah 298 Super User 2026 Season 1
