If a workflow is in an error state, does it cause any issues from a health & performance point of view if it left in this state, or should it be cancelled. This is where a workflow has triggered the start of another in the chain, but the initiating workflow has resulted in an error after successfully starting the next workflow. No further steps are in the initiating workflow except action End Workflow.
Page 1 / 1
Is this in regards to Hawkeye or just Nintex workflows in general?
In my opinion, I recommend terminating the workflows in an error state and then figuring out why the "error occurred".
While the workflow is no longer taking up resources and executing actions, it is still in the queue for the workflow engine to see if anything needs to happen. So while the impact is negligible, over time and if you have a lot of these, you may start to see issues.
Think of it as bad fruit. They still take up space and are being passed over, but over time, if not taken care of, they will cause problems.
Hope this helps!
Reply
View our Community Site Map
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.