docs(nestjs): Document SentryCron monitor config from @Cron

[wedamija]

DESCRIBE YOUR PR

Documents that @SentryCron now sends the schedule and time zone of @Cron on the same method, so check-ins create the monitor. Covers the server time zone default, which schedules send no config, and the fromCronDecorator: false opt-out.

SDK change: getsentry/sentry-javascript#25013. Merge after it ships; the page marks it as available since 11.5.0, which assumes it lands in the next minor.

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 2, 2026 10:11pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 2, 2026 10:11pm UTC

[cursor]

The plan checks errors on the changed guide pages, loads of those pages, and site error volume. An issue escalates when those page errors appear or site errors rise.

Services: sentry-docs.

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

Plan

What changed

The NestJS Cron decorator docs now describe auto monitor config from @Cron. Readers who omit a schedule see that check-ins send the Cron schedule and time zone. The sentry-docs service must deploy before this section is live. The text is marked available since 11.5.0.

Risk

Wrong MDX can fail both pages that share this include. A broken code block can fail the shared code tab on those pages. Readers can then miss how to create a monitor from @Cron.

Intended effect

This change is a docs edit. No queryable signal shows the new section is live. absent is the normal telemetry state. Do not treat a zero counter as failure.

Regression watch

This include ships on the NestJS Cron decorator page and the NestJS crons setup page. A render fault would show as errors or a drop in NestJS guide loads.

Signal	Baseline	Window	Rule	Source
NestJS guide page errors	0 events. Error rate 0% against 123 guide loads	2026-10-01T22:30:00Z to 2026-10-02T22:30:00Z	Hold at 0	Sentry project docs. Production errors whose transaction or url contains nestjs
Docs production errors	0-22 events per hour. 154 events in 24h	2026-10-01T22:30:00Z to 2026-10-02T22:30:00Z	Hold in the 0-22 per hour band	Sentry project docs. environment:production error count
NestJS guide pageload and navigation	123 spans. p95 24.6s	2026-10-01T22:30:00Z to 2026-10-02T22:30:00Z	Volume should stay near 123 per 24h. p95 should stay near 24.6s	Sentry project docs. pageload or navigation spans whose url contains javascript/guides/nestjs

The 24h p95 may include slow navigations. Escalate when NestJS guide errors leave zero or site errors leave the hourly band.

Not observable

Whether the new heading is visible on the published pages. Traffic on the sentry-cron-decorator page alone had no traces in this window. Whether the JavaScript SDK ships the 11.5.0 Cron behavior.

[sentry]

Bug: The documentation for fromCronDecorator: false is for an unreleased SDK feature and may become incorrect if the final implementation uses a different name.
_{Severity: MEDIUM}

Suggested Fix

Confirm the final property name from the corresponding SDK implementation (sentry-javascript PR #25013) once it has been released. It is recommended to merge this documentation change only after the SDK feature is shipped to ensure accuracy.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: includes/nestjs-sentry-cron-decorator.mdx#L50-L56

Potential issue: The documentation introduces the `fromCronDecorator: false` option,
which is tied to an unreleased SDK feature (version 11.5.0). The pull request notes that
this documentation should only be merged after the SDK feature ships. Because the
feature is not yet released, the final property name in the SDK might differ. If the
name changes, the documentation will be incorrect, and users attempting to use
`fromCronDecorator: false` will find that it has no effect, causing confusion.

_{Did we get this right? 👍 / 👎 to inform future reviews.}