Skip to main content

Notifications

Microsoft Dynamics NAV (Archived)

Workflow gets stuck

Posted on by 566

I have been using standard Workflow for approval Credit limit in a Sales Order in NAV 2016 for a month and has been working ok.

Three days ago, this workflow gets stuck, I mean, users hit "Send for Approval" in sales order, and workflow routine works, but it does not create an approval entry (as it used to do) and does not let Release Sales Order.

I have tried deleting the workflow and re-creating it but it keeps doing the same.

I have check workflow log and it seems to get stuck after RUNWORKFLOWONCUSTOMERCREDITLIMITEXCEEDED...

this function should change sales order status to Pending Approval, but it does not, in fact, order status keeps "Open", and not approval entry is created.

Here is the log:

ID Workflow Code Workflow Step ID Entry Point Status Type Function Name Created Date-Time Created By User ID Last Modified Date-Time Last Modified By User ID Previous Workflow Step ID Next Workflow Step ID Record ID
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 328 No Inactive Response RELEASEDOCUMENT 13/07/2016 20:59 DOMAIN\ADM 327 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 327 No Inactive Response CREATEANDAPPROVEAPPROVALREQUESTAUTOMATICALLY 13/07/2016 20:59 DOMAIN\ADM 326 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 326 No Inactive Response SETSTATUSTOPENDINGAPPROVAL 13/07/2016 20:59 DOMAIN\ADM 325 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 325 No Active Event RUNWORKFLOWONCUSTOMERCREDITLIMITNOTEXCEEDED 13/07/2016 20:59 DOMAIN\ADM 13/07/2016 20:59 DOMAIN\ADM 307 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 324 No Inactive Response SENDAPPROVALREQUESTFORAPPROVAL 13/07/2016 20:59 DOMAIN\ADM 13/07/2016 20:59 DOMAIN\ADM 323 311
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 323 No Inactive Event RUNWORKFLOWONDELEGATEAPPROVALREQUEST 13/07/2016 20:59 DOMAIN\ADM 311 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 322 No Inactive Response SHOWMESSAGE 13/07/2016 20:59 DOMAIN\ADM 321 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 321 No Inactive Response OPENDOCUMENT 13/07/2016 20:59 DOMAIN\ADM 320 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 320 No Inactive Response CANCELALLAPPROVALREQUESTS 13/07/2016 20:59 DOMAIN\ADM 319 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 319 No Inactive Event RUNWORKFLOWONCANCELSALESAPPROVALREQUEST 13/07/2016 20:59 DOMAIN\ADM 311 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 318 No Inactive Response OPENDOCUMENT 13/07/2016 20:59 DOMAIN\ADM 317 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 317 No Inactive Response REJECTALLAPPROVALREQUESTS 13/07/2016 20:59 DOMAIN\ADM 316 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 316 No Inactive Event RUNWORKFLOWONREJECTAPPROVALREQUEST 13/07/2016 20:59 DOMAIN\ADM 311 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 315 No Inactive Response SENDAPPROVALREQUESTFORAPPROVAL 13/07/2016 20:59 DOMAIN\ADM 13/07/2016 20:59 DOMAIN\ADM 314 311
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 314 No Inactive Event RUNWORKFLOWONAPPROVEAPPROVALREQUEST 13/07/2016 20:59 DOMAIN\ADM 311 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 313 No Inactive Response RELEASEDOCUMENT 13/07/2016 20:59 DOMAIN\ADM 312 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 312 No Inactive Event RUNWORKFLOWONAPPROVEAPPROVALREQUEST 13/07/2016 20:59 DOMAIN\ADM 311 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 311 No Inactive Response SENDAPPROVALREQUESTFORAPPROVAL 13/07/2016 20:59 DOMAIN\ADM 310 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 310 No Inactive Response CREATEAPPROVALREQUESTS 13/07/2016 20:59 DOMAIN\ADM 309 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 309 No Inactive Response SETSTATUSTOPENDINGAPPROVAL 13/07/2016 20:59 DOMAIN\ADM 308 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 308 No Active Event RUNWORKFLOWONCUSTOMERCREDITLIMITEXCEEDED 13/07/2016 20:59 DOMAIN\ADM 13/07/2016 20:59 DOMAIN\ADM 307 0
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 307 No Completed Response CHECKCUSTOMERCREDITLIMIT 13/07/2016 20:59 DOMAIN\ADM 13/07/2016 20:59 DOMAIN\ADM 306 0 Sales Header: Order,006160067
{7777b256-2a91-41f4-abe9-f6063a1ec84b} MS-SOCLAPW-01 306 Yes Completed Event RUNWORKFLOWONSENDSALESDOCFORAPPROVAL 13/07/2016 20:59 DOMAIN\ADM 13/07/2016 20:59 DOMAIN\ADM 0 0 Sales Header: Order,006160067

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Workflow gets stuck

    Hi,

    We've discovered to have a similiar issue at one of the Customers. We've discovered the only solution is to clear out the Approval Entry table. The workflows then get back to normal. We are running 2016 CU 3 and are now testing the newest CU so it's possible this is already sorted out there.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Workflow gets stuck

    Sorry workflow is doing this - but it's hard for me to see the error in here.  If you send me more details I can take it up with the team and see

    Can you please send me your workflow (you can export workflows as files), and a screenshot of your user setup.  Include any other info you think is relevant too.

    sglasson@microsoft.com

    Thanks,

    Stuart

    PM Dynamics NAV

  • Verified answer
    AntonioTorre Profile Picture
    AntonioTorre 566 on at
    RE: Workflow gets stuck

    Thanks jonathan

    No object changes

    Updated to CU09 but worked fine after that...  failure came later on

    I found a workarround: reseting nav service...

    Reported to ms connect to see if this happens to any other users..

  • Verified answer
    keoma Profile Picture
    keoma 32,675 on at
    RE: Workflow gets stuck

    first restart nav service.

    if that does not help, check if there were changes on nav objects the last 1-2 weeks. maybe there were changes, which concern the workflow. if so, import the old versions.

    did you update to a new CU ?

    check windows eventlog on the server, if there are according error/warning messages.

    activate changelog, add workflow tables if needed, start workflow routine again, check changelog.

    try the same steps with a demo database (cronus) on the same nav build number. check if it works or if you get the same behavior.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

New! Quick response templatesâš¡

Save time with the new custom templates!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,219 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,056 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans