D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

Stopped (error) after invoice approval completed

  • 1.  Stopped (error) after invoice approval completed

    Posted Feb 09, 2021 10:44 AM
    I'm experiencing a situation where AP Invoices go through the approval workflow and a "Workflow stopped (error)" comes up when the automated task of posting the vendor invoice is called.  The Stopped (error) gives no explanation at all of why it occurred.
    This does not happen to all invoices and  there does not appear to be a pattern (some have PO's while others don't).
    We have recalled and submitted to have some post as they should on the 2nd try, but others error out a 2nd time.
    I am operating in AX2012 R3.
    Any thoughts out there or direction to go to figure this out.

    Wes Mangum
    National Cable Satellite Corporation d/b/a C-SPAN
    Washington DC

  • 2.  RE: Stopped (error) after invoice approval completed

    Posted Feb 17, 2021 11:42 AM
    Hi Wes,

    Is the workflow designated to go to a specific user or hierarchical user? Sometimes, in the hierarchy, if there is not a level above the person who submitted the workflow, then you can get that error.

    Let me know if this has been resolved or if you have come across any other details/patterns in the last week!

    Kelly (Kane) Gustafson
    Customer Experience Manager
    Ellipse Solutions LLC
    Dayton OH

  • 3.  RE: Stopped (error) after invoice approval completed

    Posted Feb 18, 2021 09:32 AM
    Hi Wes,

    We experience this and what I am finding is that it is happening to vendor invoices after the submit button is clicked a second time. For some reason, if you recall a vendor invoice from workflow, the submit button becomes available again immediately after recall (I have noticed this in testing). The invoice is resubmitted and I am not sure if the recall is ignored from the first workflow and both try to occur at the same time. Often we are finding the auto post routine fails, because the invoice is already posted. It happens so infrequently, that we haven't gone to Microsoft with this. We just delete the workflow instance from history and move on. I am not sure if this what you are finding in AX2012, but this is what we have been experiencing in D365.

    Esther Paradoski
    Ducks Unlimited Canada
    Stonewall MB

If you've found this thread useful, dive deeper into User Group community content by role