Reliable HTTP cron and delayed-job scheduling with automatic retries and full run logs — delay.run
A subscription renewal fails. The card was declined: insufficient funds, expired card, the bank's fraud check, or a vague "do not honour". Somebody has to decide when to try again, how many times, and what to tell the customer in between.
Most payment providers will do this for you. They offer automatic retries, often marketed as "smart" because a model picks the retry time based on patterns across many merchants' card data. Or you can turn that off and run your own schedule: a job that retries on day 1, 3, 5 and 7, emails the customer, and downgrades the account at the end.
Both approaches have real defenders. Our most-discussed post so far was a case study about a retry schedule that went wrong, so I suspect there are opinions out there. Let's argue about it.
The case for letting the provider retry
They have more data than you. A provider sees millions of declines across many merchants and banks.…