Developer Discovers Sentry Cron Monitor Was Silent Due to Missing Config Object
A developer building a Cloudflare Worker fleet monitor found that Sentry's cron monitoring was never actually active, despite no errors appearing during deployment. The tool, workers-monitor, was designed to send Telegram alerts when services failed, with Sentry added as a fallback to catch silent failures. The bug stemmed from calling Sentry.withMonitor() without a required schedule configuration object, meaning check-ins had no cron context to attach to. The issue only came to light when the developer opened Sentry's Monitors page to record a demo video and found no cron monitor had ever been registered. The fix required just one additional config object with crontab schedule, margins, and timezone — amounting to 14 line insertions across a single file.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in