The ablity to rerun a workflow, especially one that starts from a form
I had a workflow that failed from a form start and had no way to restart the workflow or retrieve the information that had been entered into the form. Once I fixed the error in my connections, I couldn't rerun it. I also couldn't access the initial information in the form. The data the user had entered is lost and I can't track down any information about what was submitted.
Nicholas Kotze commented
Hi, do we know if this is likely to be available anytime 2022? Deal breaker for a present customer who would like to work with NWC. Three extra votes from me :)
Error Handling in WFC. We need a way to handle errors in WFC. Having critical workflows crashing and having to restart them is a huge issue and can cost lots of time and money for the organization.
David Johnston commented
Critical from my perspective to have that. We've had credentials for a sharepoint connector expire today (and I can imagine we'd have connection issues/outages unrelated to credentials from time to time).
We just need to be able to restart the Workflow from the point it failed once an issue like that is resolved. Happy to chat further if you still want.
Andre Andersen commented
Workflows fail from time to time. Having the ability to resubmit the start data directly from NWC would be really helpful. It is especially tedious if the workflow is a component workflow with start variables or the workflow starts with a form.
Andrew Blinco commented
Hi Rick, I have a specific requirement. A task is assigned to a user who is not a user in Nintex causing it to fail. We need to manually add the user as a participant and then restart the workflow.
Thanks for your comment.
>But if the value being used in the action configuration requires updates? This may require more thought.
-->I'm not sure what you meant this point, but what we are asking is to be able to resume the workflow, not all the failed instances but those which were failed due to HTTP429 error like throttling and/or due to time-out error for some reasons while connecting.
AdminJoshua (Product Manager, Nintex) commented
Noted on the Restart to Resume - it will depend on the error state of the workflow - IF purely resuming due to time out issue, then for sure. But if the value being used in the action configuration requires updates? This may require more thought.
Thanks for your feedback.
Just to avoid the misunderstanding, I would like to rephrase the word "Restart" to "Resume".
When the workflow is failed, we want to "resume" it from the point where it's failed, not starting all over again.
When the workflow is suspended, we can see the instance details from "Instances" tab, but there is no function to restart the workflow.
It would be good to have a restart function, at least, when it's failed in SharePoint connector such as HTTP429 error or 9min time-out.
The ability to restart / resume a failed workflow instance once the workflow has been updated and republished is a really needed feature. It would also be very useful if workflow variables could be adjusted prior to restarting / resuming the workflow.
Deanna Velasco commented
This would be extremely helpful to us. Any updates on if it is on the roadmap?
This is starting to become a pain point for us the more workflows we push out, any updates?
Philip Duggan commented
Hi Kate, any ETA on this?
Would like to restart the workflow from within a workflow instance, so it does not need to be terminated and restarted from the beginning.