I have a flow with auto resolve enabled and branches. If it logs an error on the first branch, and then I rerun it with the same record but process it through the 2nd branch, I would expect it to auto-resolve the error on the 1st branch. The trace key value is the same on both runs. However, it does not resolve the branch 1 error. The snip below shows the results after the 2nd run which went through the 2nd branch.
Hello Jim,
I am posting the expected behavior here just in case other users need some clarity on how auto-resolve behavior works in integrator.io.
The key takeaway is that auto-resolve is scoped specifically to the individual step, not the flow as a whole. Because flow steps (including those in different branches) are independent of each other, an error generated at one step will not be automatically resolved by a successful execution at a different step—even if the record and trace key are identical.
Key details to keep in mind:
-
Step-Specific Logic: For an error to auto-resolve, the record must be successfully reprocessed through the exact same step where the error was originally triggered.
-
The Workaround: If your process results in "resolving" an issue via a different step or branch, we recommend using the "Error automation via integrator.io APIs" template. This allows you to programmatically clear those errors once the record is successful elsewhere.
-
Ignore Filters: If a record is reprocessed through the same step but is skipped by an "ignore" filter, the platform will still auto-resolve the previous error for that step.
We’ve flagged this with our documentation team to ensure our help articles are updated to explicitly define this step-specific behavior.