Error Handling

As currently implemented error handling isn't terribly useful. Pausing doesn't provide much benefit versus instance failure. It would be better to be able to actually handle errors in the workflow. For example renaming a file in Sharepoint will cause an error in NAC if the destination file name exists. The alternative is to manually call the Sharepoint web services to get files with names like then manually implement a very complex component workflow that increments the file name. It's easy to say this should fall on the owners of the platform where the web service resides but that level of control isn't possible. Instead the flexible nature of web services and response codes should be able to be handled by any calling system. This is an important feature for demonstrating resilience, quality, availability, and value.

Hi all,

As you may have seen, we recently announced an Error handling capability in Nintex Automation Cloud:

Error handling can now be enabled for workflows. When a workflow encounters a recoverable error, the instance will pause, allowing users to investigate, remediate, and resume the instance from the point of failure. The failing action can be rerun.
Existing workflows will need to have its settings updated and republished and all new workflows will have error handling enabled by default. For more information, see the Error handling help topic.

Thanks again for all of your votes and input into this idea.

Regards,

Kate Huynh

Hi all,

Thanks for your submission, votes, and input.

Our teams have commenced work on Error handling, a feature which will pause instances (instead of Failing them), enabling users to address potential causes for the failure and rerun the failing action.

This feature is expected to be released in the next quarter - Q2 CY2024.

Regards,

Kate Huynh

Is there an ETA for this one please? I see it is in a planned status.