Views:

Applies to Product - Dynamics 365 Finance


What’s happening?

  1. Batch jobs are hanging or failing to execute, particularly in the context of revenue recognition and deferral schedules.
  2. The system is unable to create recognition journals when a workflow is required.

 

Reason:

  1. For batch jobs hanging, the underlying issue may be related to SQL custom queries causing deadlocks, high CPU consumption, or incorrect date filters in the batch job parameters.
  2. The recognition batch processing may not be functioning correctly due to the session date being used as a cut-off date, which conflicts with the added date criteria on the deferral schedule.

 

Resolution:

  1. To resolve hanging batch jobs:
  2. Utilize the Enhanced Batch Abort feature to abort batch jobs that are stuck in the "Executing" or "Cancelling" state by restarting the batch servers running those tasks.
  3. Enable the feature in the Feature Management workspace.
  4. On the Batch job page, select the batch tasks and click on "Abort."
  5. Confirm the action in the dialog box that appears.
  6. For further details, refer to the public documentation on canceling a running batch job.
  7. For recognition journal creation failures:
  8. Ensure that the session date is set appropriately as it acts as the cut-off date for all selected deferral schedules.
  9. Confirm that all necessary configurations in the subscription billing module are completed, including defining main accounts for deferred revenue and costs.
  10. Check that the project stage is set to one that can be invoiced from Project management and accounting parameters.
  11. If issues persist, consider working with the internal development team to customize the code to meet business needs.
  12. If the issue continues for single batch job , escalate the case to the Job Owning Team rather than Batch PG Team. for further investigation .