Forum Discussion
SharePoint Workflows: Extend Timeout
Craig Lamb SharePoint 2016 uses new workflow engine. You can check the blog post http://www.andrewconnell.com/blog/publishing-custom-events-to-sharepoint-2013-workflowson how to use Custom Events for Long Running External Processes.
Let me know, whats your environment, is it ON-PREM or O 365-SPO and whats you exact requirement .
If its ON-PREM you have the freedom to play along with the rich set of SSOM APIs.you can have a look at the SharePoint's social.msdn forum that has dedicated workflow related categories and source code available . Myself too posted many answers specific to workflow,- whether its sequential or state machine.
If its SPO Env,you have to look at declarative workflows mentioned by Devendra Devendra Velegandla .
As noted above, we attempted the following...
stsadm -o setproperty -pn workflow-eventdelivery-timeout -pv "45"
SharePoint let is do it and we see the value stored; however, it's not honoring. I am just trying to find the easiest way to get SharePoint to honor our WF's for more time without having to redo everything. That would negate 3 years of confidence, field validation, etc.
- The same workflow works fine for other items in the list. It is just failing for a large item that takes longer than 20 minutes to run. I don't believe that it's our code, it's the fact that we need the workflow to run longer that SharePoint allows. We may need to implement an event or something that tells WF to wait. We just need WF to run longer.
Craig Lamb whether the task list associated with your splist is crossed the threshold of 5K items ?
Do you have managed metadata columns(taxonomy) associated with workflow ?
Do you have more than 8 lookup columns or people picker columns in your SourceList?
Have you used content types in your workflow? if yes,how these content types are deployed( the best practice is to deploy the content type& workflow as a feature ) at the site level and activate it in Order ( this activation /deactivation of feature should be in a specific order else, WF will fail).
There may be many reason for your WF termination.
Did you analyse logs folder/log files through which you may get a hint, whats happening in the Env.? <p>
One more thing you can try, in the workflow, you can add a logtohistoryactivity and log all these actions,write into an text file, thus, you will be able to track the source of error. At what point , its failing. Or simply a codeactivity and inside this codeactivity, you write the values,into a text file.
it may also be important that, any of the columns in your soucelist is accidentally deleted by your teammembers and they recreated thus the internal name in the CAML query might have changed...