Skip to main content

A patch was applied this week that caused all workflows to stop running. We have a site workflow that runs on a schedule that failed. The stored procedure rptErroredWorkflows is showing that it is in error. Going to the Site Workflow page it shows that it 'Failed on Start'. The detail page shows that it was cancelled just after failing (same time stamp).

So I believe what happened was the cancel failed, since the time stamp was prior to my implementing the fix for this problem. How can I go about getting this workflow into the correct status?

With the timing of this, I almost wonder if you are just experiencing what's described over here:  

Using the links we've posted in the thread you should be able to fix your problem and enable workflow running and publishing again. 

The workflows are running. That MS Patch issue was patched and the issue related to that fiasco resolved before I posted this question. The problem is there are a few site workflows that failed on starting during the time it wasn't resolved and I would like to know how to get rid of the error status on the site workflows just so that it doesn't keep showing up in my rptErroredWorkflows results. I know I can go into the workflowInstance table and update the status from 64 to 4 but thought I'd check to see if three is a more 'supported' way of accomplishing this.

Each week i run this store procedure and save the results to a table. This helps me keep an eye on failures across 180 sites. So when i see an error I go and get the details and then resolve them. Having these show up is a red herring that I don't want to see week after week.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings