You are viewing limited content. For full access, please sign in.

Question

Question

"Runaway" Workflow caused by recursive rule - best options to terminate instances?

Workflow
Updated November 16, 2022
asked on November 15, 2022

Hi,

Have a workflow that has (an unfortunately) coded rule which caused it to go in recursive calling of the same workflow. After disabling the rule, the outstanding instances open are blocking up resources on the Workflow server. Is it best to delete and purge the document being used by these workflow instances queued up? OR is there another way to terminate 300,000 workflow instances? 

Thank you.

0 0

Replies

replied on November 15, 2022 • Show version history

You can of course just terminate them from the search or from the Workflow admin console

But if for some reason that isn't working for you, here's an idea to try, not entirely certain if it will work...

This assumes you don't have other instances of this workflow running that are valid and accurate.

Disable all the starting rules for the workflow.  Edit the workflow.  Disable all parts of the workflow.  Publish the workflow.  When it asks if you want to update the workflows in progress, say Yes.  All running workflows should now end up finishing since all components are disabled.  Once you are sure nothing is running, you can go re-enable components and starting rules as needed.

0 0
replied on November 15, 2022 • Show version history

Thank you for your reply.

I did try this by placing a conditional sequence at the start of every tasks in the workflow that if the starting entry is related to the rogue entryID then terminate but it does not update the "waiting" workflows only those that are "running". I believe it requires database intervention to stop WF services picking up left over ones where services are restarted.

0 0
replied on November 16, 2022 • Show version history

It sounds like maybe you are adding a step prior to the step the instances are at, so the ones in progress won’t be impacted by the change because they are beyond that point.  That was why I was thinking to just disable everything in the workflow to ensure whatever step it is on ends because it is now disabled.

But I could be wrong and it won’t impact a step that is actively waiting for something to happen. In that case, you may just need to terminate them manually from the search screen.

0 0
replied on November 16, 2022

I have nearly cleared them all. I found by disabling all the rules on all workflows on that server helped with performance and quantity being closed

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...