It is important to note, however, that 3rd party services will have their own policies on what is considered an error.
For example, when trying to retrieve a non-existent record in Salesforce, the Salesforce API will not return a 404 error.
Rather, it will return an empty array.
In this case we can use a boolean condition to check for an empty array and then take whatever action we feel necessary.
We could send an alert via email or to a Slack channel:
Or we could force an error as explained below:
In the example above you could force an error using the Terminate connector 'fail run' operation:
This would trigger a run of an alert-triggered workflow and pass on the message you have set:
Note that, rather than allowing a workflow to error, you can also potentially make use of Fallback values to use e.g. empty strings, null values or default email addresses, phone numbers etc.
When using legacy manual error handling mode, only third party errors can be handled manually at the connector level. Alerting workflows should be used to monitor workflows using legacy manual error handling. To enable or disable legacy manual error handling please see the workflow settings.
To ensure compatibility, workflows by default will continue to use legacy error handling behaviours. This can be changed in your workflow settings. Please see below for a comparison of behaviours.
Legacy Manual Error Handling Not Enabled | Manual or continuous modes supported for all errors without automatic behaviours. |
Legacy Manual Error Handling Enabled (default) | Manual or continuous modes do not support all errors, where supported automatic behaviours take precedence. |