You’re offline. This is a read only version of the page.
Announcements
10
Hi - We use Purchase invoice journal workflow for approving ad hoc vendor invoices. Its quite simple and has worked well for a long time.
I have discovered a new issue which I I think may be a bug but either way I cannot recover the workflow.
Here are the steps:
- New Invoice Journal created with multiple lines
- Submitted to workflow
- Journal Validated by user which shows a warning that some of the invoice numbers entered had already been used (we prevent duplicate invoice numbers by vendor)
- Journal recalled so it can be edited
- Workflow stopped with Unrecoverable status and error message "Stopped (unrecoverable): Journal APInv, JBN0001525 is being posted and the workflow status cannot be changed"
There is no option to Resume, Recall, Reassign the workflow. It seems to be truely "unrecoverable".
I suspect that by validating the Journal, it has somehow linked this to it being posted (which it can't be as workflow was never approved) and workflow is now trying to recall what it thinks is a posted journal, even though it isn't posted, and is erroring as a result.
My question is how can I get this journal back to a state where it can be edited? My worry is that because the lines exist, we can't just key a replacement journal as AX will validate the invoice numbers against the now stuck journal.
Many Thanks
Hello Darren Crisp,
Great.
Many thanks for the update.
Would be great if you could keep us updated how things are going and whether you need some additional help from the community.
Best regards,
Ludwig
Thanks for the feedback. I have contacted our MS Partner for support.
Hello Darren,
I have checked LCS and no similar scenario has been reported to Microsoft Support. I would encourage you to log a new service request to Microsoft support so we can review the functionality and correct it - if necessary.
Regarding the blocked Journal - you can also ask MS support to unlock it. We should be able to change status back to draft.
Hi,
Have you checked the available hotfixes on LCS already?
It might be the case that this is a known / old bug for which a hotfix is already available.
Best regards,
Ludwig
#1
André Arnaud de Cal...
294,261
Super User 2025 Season 1
#2
Martin Dráb
232,994
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
