I have a user that has an infinite loop going, and not sure how to kill it. Even after terminating the workflow it is still running (sending email notifications). Safe looping is not enabled due to business requirements. Any suggestions?
Solved! Go to Solution.
You may have to delete the item and then look in your timer jobs to kill that job. The timer job is almost your last resort but if you really need it to stop, I would go there and kill the timer job that is running. This will affect any and all other workflows within that site collection or web app, but again that should do the trick.
Eric, we had some scheduled maintenance run at 1am, that I think kills timer jobs; in any case the moment the maintenance began, the loop was killed. For future readers, deleting the item (and clearing from the recycle bin) and deactivating the Nintex features for the site collection had no effect. Interestingly, when I reactivated Nintex, the workflow reappeared, so I don't know if manually deleting the workflow itself (after exporting it first, of course) would have made a difference. It would be nice if Ninex provided steps for how to kill an infinite loop, should it happen--even when safe looping is enabled (as safe looping doesn't kill an infinite loop, it only slows it down). For some environments, safe looping isn't a viable option due to business requirements workflows serve.
Thanks for your quick response, it did help move the discussion along with our admins. Shalom.
If you are stuck in a loop and safe looping is on, you should have no issue going to the workflow status page and hit Terminate Workflow(or End this workflow).
I've killed an infinite looping workflow with safe looping off the same way before. Was this not an option, or did it error when terminating?
For the non-safe looping off scenario, I see what you meant know, sorry. Once you terminate the workflow, all of the already delivered actions to the engine will fire. Once you terminate, there will be no more items generated or activities to be worked on. So yes, the only way to stop that is to stop the timer job or wait it out.
Hello there... no solution for this? We have a similar situation in our production environment. We have restarted the SP time job. No luck. The WF, the items are deleted and cleared the recycle bin as well. Thanks for any help...
Yep. It didn't
Raised a High prio ticket to Nintex, but they never got in touch so far.
We decided to leave it as it is for the night since the WF was just sending notifications and did not have any major computations (hoping that Nintex will get back by then). The CPU/DB usage was also manageable, not too high. It finally stopped sending emails after 11 hours...
Following up to what Andrew shared. Can you verifiy the following:
Those steps should help resolve the issue.