Short answer: For scheduled data cleanup, use the cron scheduler your team already operates, then put retries behind a durable worker and make every reconciliation effect idempotent; trigger price matters less than recovery behavior.
I've been paged by missed jobs and duplicate deliveries. Those incidents leave the same runbook note: a schedule is a hint that work should begin, not proof that it ran once. In a property management system, a duplicate reconciliation can notify a tenant twice or apply the same correction twice, while a missed run can leave yesterday's payment-provider records unmatched. The useful invariant is narrower: for a given property, provider account, and settlement date, every intended mutation has one stable idempotency key.
Retries are normal. Repeated side effects are a design error.
How should teams compare cron schedulers for scheduled data cleanup?
It shouldn't own the whole recovery policy. A scheduler should create a run request with a deter
Discussion
Your thoughts matter!
Your input is valuable—be the first to share it!