The least complex design is a cron trigger that calls a public webhook, waits for that webhook to enqueue the reminder work, and lets an idempotent worker perform delivery. Cron decides when an attempt starts; it does not prove that every subscriber received a shipment update.
How do I use cron to trigger webhook tasks for user reminders?
The page fires at 09:00, but the useful signal is not “cron ran.” It is closer to “the scheduled run produced no accepted queue message” or “the queue has stopped making progress.” An on-call engineer should see a schedule identifier, the attempt status, and a request ID. The payload should contain only the reminder facts needed by the worker, not a full student record.
Work backwards from that page. A publicly reachable cron URL invokes the webhook. The webhook validates the request, publishes one message per required subscriber, and returns a small success or failure status.…