Cron scheduler seems to throw a timeout

Bugs
4

Thanks @xlarry

Yes, the 429 responses and the attempted retrying by manually waiting within the code step is most likely the culprit here.

When using a 3rd party NPM package or manually using setTimeout in a code step, it’s still affecting the total execution time of the workflow.

You might have more luck with the built in $.flow.rerun method to rerun an API request in case you hit an API limit.

The advantage there is the pausing between reruns will not add to your overall execution time.

Below is a link to the documentation:

Here’s a short video on how to use it:

Hope this helps!