Views:

Applies to Product - Dynamics 365 Finance


What’s happening?
Batch jobs, specifically Firming Batch jobs, are intermittently becoming stuck in an executing state, causing delays in processing.
 

Reason:
This can occur due to several reasons: - A high volume of batch tasks queued at the same time. - Batch restarts occurring during execution. - Application Object Server (AOS) restarts during multi-threaded firming processes.
 

Resolution:
To resolve this of batch jobs becoming stuck in an executing state, follow these steps:

  1. Abort and Reset the Batch Job:
  2. Use the enhanced batch abort feature to cancel the executing batch job. Refer to the following documentation for detailed instructions:
  3. After aborting the batch job, rerun it to ensure it completes successfully.
  4. If the issue persists after using the enhanced batch abort feature, raise a support ticket for further investigation.
Note: Batch jobs typically hold termination until all currently running tasks under the batch job are finished executing. Telemetry may not always explicitly show a batch job as "stuck" if some tasks complete successfully while others encounter errors or delays.