Cron Expression Tester from Sandglass helps you validate when a cron schedule will actually run. Use the result to decide what to monitor continuously.
Reach for this when you need to validate when a cron schedule will actually run during setup, debugging, or an incident review. A one-off check is useful for diagnosis, but production systems need continuous monitoring once the immediate question is answered.
Use the tester to confirm the next expected run times, then set a heartbeat interval with a realistic grace period so normal scheduling jitter does not raise false alarms.
A schedule that looks right can still surprise you across time zones and daylight-saving changes. Verify the concrete next run times rather than trusting the expression at a glance.
Use the output to confirm the current state, and treat anything surprising as a starting point for diagnosis rather than a verdict.
Write down which results count as healthy, degraded, or failed before you automate anything.
Recreate the same check in Sandglass on an interval so the next change is caught automatically.
Send failures to email, a Slack webhook channel, or a generic webhook owned by whoever will fix them.