RELATED IDEAS
Error Handling
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.
1
MERGED
2
MERGED
File locked by shared use - please provide an action or error handling that resolves this issue
Please provide a solution for this issue. This issue is causing us major problems and every OOO solution we come up with is 10x the work only because the workflow can’t handling waiting for file to be unlocked by user to move forward or allow us t...
2
Completed
1
MERGED
NWC - Error handling in Query user profile action
Error handling feature is not present in Query user Profile action in NWC.On-prem version has this feature which is very helpful in Site workflows.When an user doesn’t exist then we have the option to log it and proceed with rest of the users. Thi...
0
Completed
1
MERGED
Do not crash the workflow when a member cannot be removed from a SharePoint Group
Please do not crash my workflow in the action "Remove user from a SharePoint Group". It is absolutely wonderful that you return an object that tells me if the removal was successful or not. That is exactly how it should be for every action. BUT (c...
1
Completed
1
MERGED
Do not crash the workflow when a member cannot be added to a team in MS Teams
When I add a member to a team in MS Teams and it cannot be added for whatever reason currently the workflow bluntly crashes. Please don't do that to us ;-) That is sooo 2020. Can you please return an object that tells me if it was successful or no...
1
Completed
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:
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.