Hi Hariprasath Udayakumar This idea is in our backlog. You can find it on our product portal (link). Please upvote and share any inputs you have. Could you also share the types of repetitive error...
Michael Pilgrim You can explore multiple ways to achieve it: Refer section "Send errors to an integrator.io listener (custom script)" on link Generate a flow event report link Get a list of erro...
We should also come up with another cool badge for you Steve Klett :) We will evaluate your suggestion, thanks!
Jolyon Blazey Thank you for sharing the use case and the requirement. We have this feature (i.e. access to success and ignored records) in our backlog and will prioritise it.
Yes. In fact, 'Auto-resolve' features takes care of 3 things (link): clearing up duplicate previous run errors, auto-retrying and auto-detecting a connection when it's back online. When it's set to...
Hi Bas van Ditzhuijzen,You can disable "Auto-resolve errors with matching trace key" to not auto-retry the errors. The field is available in Flow settings.
Thank you for your post Paul S Currently we don't support ILM for Integration Apps. You can explore ILM for custom integration for your use case. Pls refer the link for more details.
Thanks Steve Klett. We will be fixing this issue in the upcoming Nov'23 release.
The error "Failed to save record because Record has been changed" is now classified as Intermittent. We recommend keeping Auto-resolve enabled on the flow where this error occurs as integrator.io w...
Steve Klett The error "Failed to save record because Record has been changed" will be classified as intermittent and then auto-retry will kick-in. We will soon release a fix and share the timeline.