I often talk with customers who say things like "Ignore all those errors, I know about them and I just haven't cleared them out, they're not real".
There is a template for exactly this type of scenario, which the adoption team tries to tell as many people about as we can. Especially useful for expected errors, or errors you know you don't need to do anything about that just pile up.
There is a template in the marketplace that will allow you to install a flow that will take those errors and either automatically mark them resolved, or push a retry, and help keep the error queue only showing the errors you need to intervene on.
If you go to the marketplace and search error, this (and a couple other useful error tools) will show up:
Then you just follow the directions linked above and tell it the error message to look for, and when the flow runs, it will either resolve or retry the error for you.
Great tip and awesome template! We use it all the time because unfortunately there can be "false-positive" errors.
There is also another template in the marketplace called ErrorsIO-Snowflake in case you need to pull the errors for external analysis. Sometimes we use this to understand what is false-positive and then utilize the Celigo error automation template to take action.
100%! I like to rephrase errors as an indication that something needs action, not that something is broken.
Sometimes it IS something broken, of course, but a lot of times it is just things like we have both mentioned. Really helps to clean out the noise.
There is also a native in flow function that doesn't use the separate flow, utilizing trac keys to autoresolve errors. However that doesn't give the options for more advanced handling, like you mention.
