Applies to Product -Dynamics 365 Commerce
What’s happening?
The batch job for processing retail statements is skipping records and sometimes encountering errors, which affects margin reporting.
Reason:
This is caused by high CPU usage due to a large number of transactions being processed simultaneously, leading to batch throttling and potential query deadlocks.
Resolution:
- Check if the "Priority-based batch scheduling" feature is enabled.
- Ensure both "Batch priority-based scheduling" and "Batch concurrency control" features are enabled in the Feature Management workspace.
- Create a standalone batch group for statement posting related batch jobs.
- Set the "Max Concurrency" parameter to a value less than the system capacity to prevent resource starvation. For example, if the total batch threads are 24, set the "Max Concurrency" to 12.