502 Bad Gateway on API Calls causing up to 60% failure rate for cron jobs

[fable]

@Fugiman

Yes our API is flaky, yes we are working on increasing it’s stability. Most of our apps have retry logic to minimize the impact of a request failing, I’d recommend the same approach for your cron jobs. Just make sure to cap the number of retries and use exponential backoff and you should be fine.

Ah, thank you for clearing this up.
I have a single retry per failure with a 1 second delay in between at the moment.

Much appreciated!