From 832b5fc66d48e6a6033e905f12ca18e00990d7e6 Mon Sep 17 00:00:00 2001 From: Dan Fuller Date: Fri, 16 Oct 2026 18:28:20 -0700 Subject: [PATCH 1/2] docs(js): Document the graphile-worker crontab monitor config Co-Authored-By: Claude --- includes/javascript-crons-automatic-crons-instrumentation.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/includes/javascript-crons-automatic-crons-instrumentation.mdx b/includes/javascript-crons-automatic-crons-instrumentation.mdx index f8e09f95a896b..2a461cf02fcde 100644 --- a/includes/javascript-crons-automatic-crons-instrumentation.mdx +++ b/includes/javascript-crons-automatic-crons-instrumentation.mdx @@ -165,7 +165,7 @@ For cron strings, each check-in sends the schedule and time zone (your server's Requires SDK version `11.5.0` or higher and `graphile-worker` version `0.16.0` or higher. -Use `Sentry.graphileWorkerIntegration` to monitor the jobs that the [`graphile-worker`](https://www.npmjs.com/package/graphile-worker) crontab schedules: +Use `Sentry.graphileWorkerIntegration` to monitor the jobs that the [`graphile-worker`](https://www.npmjs.com/package/graphile-worker) crontab schedules. Each run sends a check-in with the crontab schedule, in UTC, so Sentry creates the monitor on the first run: ```JavaScript Sentry.init({ @@ -181,4 +181,4 @@ Sentry.init({ The monitor slug is the crontab item's identifier: its `id` option, or the task name if there's no `id`. `excludeCronJobs` skips items whose identifier matches a string exactly or a regular expression. Jobs are monitored by a process that runs the crontab, which `run()` does by default. -Check-ins are sent without a schedule, so create the monitors in Sentry first. +Items with a custom `match` function check in without a schedule, so create those monitors in Sentry first. From 118dcb259ac4a3da6c0dc7633bccf1101521709b Mon Sep 17 00:00:00 2001 From: Dan Fuller Date: Thu, 29 Oct 2026 11:04:01 -0700 Subject: [PATCH 2/2] fix(js): Say jobs with unsupported schedules aren't monitored --- includes/javascript-crons-automatic-crons-instrumentation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/includes/javascript-crons-automatic-crons-instrumentation.mdx b/includes/javascript-crons-automatic-crons-instrumentation.mdx index c8b047e3a1352..ea815c5be3155 100644 --- a/includes/javascript-crons-automatic-crons-instrumentation.mdx +++ b/includes/javascript-crons-automatic-crons-instrumentation.mdx @@ -193,4 +193,4 @@ Sentry.init({ The monitor slug is the crontab item's identifier: its `id` option, or the task name if there's no `id`. `excludeCronJobs` skips items whose identifier matches a string exactly or a regular expression. Jobs are monitored by a process that runs the crontab, which `run()` does by default. Failed runs send an `error` check-in and report the error to Sentry. -Items with a custom `match` function check in without a schedule, so create those monitors in Sentry first. +Items with a custom `match` function aren't monitored.