👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you are looking for the Nintex roadmap, you can find that on Nintex Community
If you have questions about Nintex Ideas, please contact email@example.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact firstname.lastname@example.org
Yes, this would be super helpful, especially with our library issue. At least then, we could pause workflow and loop back through some actions if needed until it goes through.
We have issues with document management right now if a user has a document open it says locked for share use or something like that. If this existed, we could resolve our issue among other workflow failure issues that we cannot get around or are caused for no reason that could be identified.
The lack of this functionality is a serious concern. It is not acceptable for a workflow to fail because NWC is unable to handle an error being returned by an API.
It would also be extremely valuable to be able to restart/skip actions from the instance details page, so that workflows that encounter unexpected issues (3rd party service down for maintenance) could still be managed.
Being able to programmatically specify what should happen if an action fails would be great. Sometimes, yes, you might just want the workflow to fail. Other times maybe it's not an issue at all and the workflow should continue. Or you might want to be able to build out some actions where it simply waits a few seconds/minutes and tries the action again.