Hey @Qirab,
Thanks for reaching out about this.
You are correct that even with an Error Catcher defined, the final integration run status can still show Failed.
The short answer is yes, you can absolutely mask a task error to make the overall integration run status show as Succeeded. For clarity, the status is not permanently set to Error immediately upon failure and it can be controlled by the configured Error Handling Strategy.
It’s the Error Handling Strategy configured on the failing task that can help dictate the final run status.
How to Override the Status to Succeeded
You can prevent the final run status from being marked “Failed” by using one of the following Retry Strategies (found in the task’s Error handling section):
1. Use the Ignore Strategy (Direct Success)
This is the simplest solution. The Ignore strategy is defined to “Ignore the failure of the task… assuming the failed task has Succeeded.” This allows the entire integration run to complete with a final status of Succeeded.
2. Use the None Strategy (Conditional Success)
The None strategy initially halts the task, but its description confirms that if an alternate path (like your Error Catcher flow) exists and “all tasks in the alternate path run successfully, marks the integration status as Succeeded.” This strategy allows you to force a final Succeeded status after a successful recovery.
For the simplest override, use the Ignore strategy. If you need robust compensation and recovery logic, use the None strategy combined with your Error Catcher to ensure the successful recovery path resolves to Succeeded.
Here’s some good reference posts aligned with your question:
- Error Handling in Application Integration
- How to test for errors on a Task in Application Integration
Hope this helps!