Skip to Main Content
Nintex Ideas

đź‘‹ 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 have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Status Planned
Categories Workflow Designer
Created by Guest
Created on Aug 9, 2022

Add "on error" option to all NWC actions

Over the last several months, we've seen "random" errors occur on well designed, hardened workflows that are in production. In many cases, even if an error were to occur, we would like processing to continue. Can we get an option to configure what should happen next if an error occurs? For example, provide and option to continue on to the next action, stop the workflow, etc. This would be immensely helpful.
  • ADMIN RESPONSE
    Sep 7, 2022
    Thank you for your feedback.  We are currently in the process of gathering more information on error types and considering different solutions and best options for fast recovery.
  • Attach files
  • Brandi Woodson
    Reply
    |
    Mar 21, 2023

    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.

  • Avi Solanki
    Reply
    |
    Mar 9, 2023

    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.

  • Brady
    Reply
    |
    Sep 7, 2022
    We're having this same concern in our organization as well. NWC can support a lot of complexity in the types of workflows designed - meaning the answer can't be as simple restarting the workflow from the beginning. In my opinion, we really need to have a way to define what happens when an action fails. Perhaps provide a toggle on each action to indicate whether a failure should terminate the workflow or not, as well as making the return code and action result available as action outputs. As Workflow designers, we could then evaluate the output to determine the best course of action.

    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.
  • Jordan Maynor
    Reply
    |
    Sep 7, 2022
    This sort of functionality would be invaluable to us. It's very frustrating designing a fairly hardened complex workflow and seeing a form go through 4 or more levels of approval only to fail on some action where it had to call out to a web service or write to an SQL server and there was a hiccup in internet connectivity at that moment. Whole workflow fails and the initiator has to put in a new form. No real fault of the workflow designer, but it makes the person putting in the form frustrated when it's a more important form that needs to get approved in a limited time-frame.

    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.
1 MERGED

Ability to restart failed action in a WFC and continue existing workflow.

Merged
Currently we have workflows where it has already has captured alot of information and WF failed due to something silly in the Workflow. Like a name of a file being the same. I was able to delete the file and I wish I was able to restart that actio...
Guest over 1 year ago in Nintex Automation Cloud (formerly Nintex Workflow Cloud) / Other 0 Planned