locked
Failed to persist workflow instance (error code 5) RRS feed

  • Question

  • hi there,

    We have a farm which is running many workflow instances. Our sharepoint logs are full of the following entries:

    Failed to persist workflow instance XXXX-XXXX-XXXX-XXXXX with error code: 5, instance data size: xxxx, internal state: xxx

    We are suspecting that this is the root cause for our extremely delayed workflow jobs (a task response may take 2 or 3 hours to complete), however I have found no resources regarding this error.

    Any help would be appreciated

    Monday, January 30, 2012 2:15 PM

Answers

  • Hi,

    When the workflow has been running for more than 7 minutes, sharepoint workflow failover timer job will treat it as a dead workflow ans reset its status. so, i think you can try to run a simple workflow to check if it is working fine, if so, please wait for the future sharepoint CU to fix this.

    Regards,

    Seven

    • Marked as answer by spyrosnb Friday, February 3, 2012 12:55 PM
    Wednesday, February 1, 2012 8:43 AM

All replies

  • Hi,

    When the workflow has been running for more than 7 minutes, sharepoint workflow failover timer job will treat it as a dead workflow ans reset its status. so, i think you can try to run a simple workflow to check if it is working fine, if so, please wait for the future sharepoint CU to fix this.

    Regards,

    Seven

    • Marked as answer by spyrosnb Friday, February 3, 2012 12:55 PM
    Wednesday, February 1, 2012 8:43 AM
  • thanks Seven. This error appears in our large workflow, but it apparently affects the execution of others that are smaller because the workflow timer job takes forever to complete.

    So the root cause is probably that each workflow instance in our big workflow is running for more than 7 minutes. Do you have any idea why this happens? Does it have to do with the workflow size? The activities that are processed in each step are not heavy, so the only think I can think of is the workflow xoml size itself that could have an impact on the execution.

    Wednesday, February 1, 2012 9:29 AM
  • Hi,

    There is no good solution for this issue except stop the big workflows or use the a series small workflows as an alternative.

    Or you have to wait the future sharepoint CU to fix this.

    Regards,

    Seven

    Thursday, February 2, 2012 5:43 AM
  • Seven,

    I'm facing the same issue, unexpected event "Failed to persist workflow instance."  We ported several dozen workflows (Nintex Workflow) over from SharePoint 2007 to SharePoint 2010.  We did not have this issue under SharePoint 2007 and have run 10,000+ workflows instances under SharePoint 2007.  Nintex's guidance, like yours, was to break these up into smaller workflows.  I have done that, but still see the same error and it is becoming a full time job manually stopping and restarting workflows to keep production approvals moving forward.

    Like many things in SharePoint 2010, I'm assuming there's a new constraint limitation that was put in place with regards to workflow hydration/dehydration.  Any idea as to how much longer we have to live with this before the next SharePoint CU is released to correct it?

    Thanks,

    Chad

    Wednesday, April 11, 2012 9:17 PM
  • Hi

    this thread is very old but as the issue seems not to appear very often I decided to update it.

    We had a similar issue with a workflow running about 90 minutes. Nintex support told us that there is a hard coded limit within SharePoint 2010 for "workflow persistence". This can lead to a scheduled workflow to loop internally - it just starts again inside the same execution (only one entry in workflow history list). 

    Our workaround was to split the workflow into several smaller parts and run them one after another.

    Regards

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE | SOLVIN information management GmbH, Germany

    Thursday, November 10, 2016 11:32 AM