Short answer: For scheduled scripts that make HTTP calls, choose backend cron alternatives that enqueue durable work; keep retries and duplicate handling outside the timer. The deciding constraint is delivery guarantees, not a bare cron trigger or a low headline price.
A scheduled media cleanup job should enqueue webhook work and make each delivery idempotent; it should not keep retrying inside the cron process. A timer tells you when to start. It does not make an HTTP request durable, ordered, or safe to repeat.
I build CLIs and SDKs for developers, so I measure the first useful call and count every piece of glue. A five-line scheduler that loses a delivery at the first network timeout is not small. It is unfinished.
What does a schedule actually guarantee?
A scheduler can provide a trigger window. The outbound request needs a separate contract.…