Comment on page
Automatic retrying of failed flows due to third party timeouts, downtimes, or rate limits
Locoia has an automatic retry logic for failed flows to handle third party timeouts, downtimes, rate limits, etc.. This makes it very convenient that if something goes wrong along the way your data and any temporarily generated data is stored and can be reused in order to continue exactly where the Flow Run was unintentionally stopped.
Automatic retrying is turned on by default, but can be turned off on a per Flow basis in the Flow's settings.
- Flow is setup or built incorrectly
- Flow is built to process data in a certain way, but there may be data inconsistencies from time to time, as usual in data handling.
- Systems or APIs that flows interact with may be down or temporarily out of service.
- Systems or APIs may have rate limits allowing only a certain number of API calls per time unit, e.g. 100 per minute is often used.
There are three different groups of errors, which have different retry logics:
When the Flow's data retention is set to 0 and an error occurs in one of the steps that falls into the first group, this step's contents will be temporarily stored and displayed in the Flow Debugger in order to make retrying possible.
In case you don't want this to happen, automatic retrying has to be disabled for the Flow