web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Workflow Issues D365 F&O

(1) ShareShare
ReportReport
Posted on by 477

Hi, I am facing some issues related to the workflow process engine where it gets stuck and now not able to reset or take any further action on it. an instance sees below.

1) Due to Period Close. The user modifies the Purchase Order and resubmits the workflow. bud it gives an error and stopped. now I am not able to recall or make request change to modify anything and resubmit the workflow.

Stopped (unrecoverable): The accounting date cannot be updated. No ledger calendar period between the document's current accounting date  1/18/2021 and max allowed date 1/1/2025 allows posting. Check the ledger calendar setup or update the document date to be within the allowed postin

2) I try to resume the workflow by finding the cause of the stopped error. till I reach the exact error which was due to the period close this particular Purchase requisition start through this error. but others get resolved when I open the period.

Stopped (error): Workflow message '{B3BD6BCB-22F5-4052-9653-C32C5FB0B49F}' has exceeded the maximum retry attempts of 5.

Categories:
I have the same question (0)
  • Anrini Profile Picture
    on at

    Please check status for the three key workflow batch processes by navigating to - System Administration > Inquiries > Batch Jobs - enter workflow in the filter field. They need to be in 'waiting ' state.

  • Sajjad_00 Profile Picture
    477 on at

    This is the first thing which I saw and found 3 in DAT company only having waiting status. the issue which I submit is different. based on my other request working normally.

  • Anrini Profile Picture
    on at

    Could you change the company from DAT to USMF or something else and check ?

  • Suggested answer
    Aymen CHELBI Profile Picture
    574 on at
    Hello,
     

    I encountered the same error message today. Although it is not very clear, after analysis, I identified the cause of the problem: the person who submitted the workflow was deactivated from the ERP following their departure. The solution is to recall and restart the workflow with another user.

     

    Best regards,

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 687 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 535 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 403 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans