A rate-limited media worker pool changes the answer. The simplest SaaS cron scheduler is the one that starts one daily run, records a durable idempotency key, and leaves retries to a worker that can prove the email was already sent. A calendar UI does not solve duplicate reports. The goal is automating a few daily tasks with minimal setup, not building another control plane.
TL;DR: use one daily schedule, a small enqueue endpoint, a durable job record, and a retry policy with explicit ownership. Keep the scheduler boring. Put correctness in the job boundary.
Keep it boring.
What makes a daily email scheduler simple?
The schedule is the easy part. A daily report email has four separate operations: decide that a run is due, enqueue work, render the report, and deliver it. Treating those operations as one request creates a bad failure mode.…