docs(cloudflare): Document opt-in Cron Trigger monitoring

[wedamija]

DESCRIBE YOUR PR

Adds a "Cron Triggers" section to the Cloudflare crons setup page for the new opt-in cronTriggersIntegration: how to enable it, the day-of-week conversion, the default slug derived from the cron expression, and the slug function with optional monitor settings.

Merge after the SDK change ships: getsentry/sentry-javascript#25014. The page says available since 11.5.0; update that if it lands in a different release.

IS YOUR CHANGE URGENT?

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

PRE-MERGE CHECKLIST

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Oct 3, 2026 12:47am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 3, 2026 12:47am UTC

[cursor]

The plan checks client errors, server 5xx responses, and page-load volume. An issue escalates when client errors rise above the measured band or any server 5xx appears. Telemetry cannot prove the new section is present.

Services: sentry-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

The Cloudflare Crons setup page now documents opt-in Cron Trigger check-ins. Readers see how to enable cronTriggersIntegration, map slugs, and convert day-of-week fields.

This change is live after sentry-docs deploys. The page path is /platforms/javascript/guides/cloudflare/crons/.

Risk

A broken MDX file can fail the static page. It can also fail the whole docs build. A wrong sample can create billed monitors. It can also collide monitor slugs across workers. Shared code-fence rendering can throw on other pages.

Intended effect

This change is a docs edit. It has no queryable product signal.

Confirmed means the Cron Triggers section is on the live page. Absent means that section is missing. Sentry cannot see either state.

Regression watch

This diff can break the Cloudflare Crons page. It can also break shared client rendering on the catch-all docs route. Transaction names collapse to /:path*?. Watches use site-wide docs production signals.

Signal	Baseline	Rule	Source
Production error events	0-22 events per hour. 155 events in 24h against 9197 pageloads, 1.7%	Hold in the 0-22 events per hour band. Escalate if the hourly count rises above 22. Do not treat continued Algolia or Kapa fetch failures at this level as new	Sentry org sentry, project docs, environment:production. Window 2026-10-01T23:00:00Z to 2026-10-02T23:22:32Z
http.server 5xx spans	0	Hold at zero. Escalate if any span appears	Sentry org sentry, project docs, span.op:http.server with status 500 or higher. Same window

Pageloads in that window were 9197 for span.op:pageload and environment:production. Use that count as the denominator. A large drop in pageloads with rising errors is a regression on the catch-all route.

Hourly error counts were lower after 09:00 UTC. The 0-22 band already includes that peak.

Existing noise in this window includes Algolia insights fetch failures. It also includes Kapa proxy fetch failures and promise-rejection captures.

Not observable

Sentry does not record whether the Cron Triggers heading is on the page. Filters on the Cloudflare Crons path returned zero pageload and navigation spans. Transaction names are /:path*?, so this page has no path-level error series.

Pageload p95 for production was 30000ms. That value looks capped and is not a useful threshold.

The sample's match to the shipped SDK is not in docs telemetry.