feat(crons): Document broken monitors feature (#15280)

## Summary

- Documents the broken monitors feature that automatically notifies
users when monitors have been broken for 14 days
- Explains the automatic muting behavior after an additional 14 days
- Clarifies notification recipient hierarchy based on monitor ownership
- Adds important notes about billing and disabling notifications

## Changes

- Expanded troubleshooting section with detailed explanation of broken
monitor detection
- Added notification recipient hierarchy (user owner → team owner →
project team)
- Clarified that muting does NOT stop billing
- Added links to notification settings and billing documentation
- Added references in job monitoring page about ownership notifications
and automatic muting

## Test plan

- [ ] Review documentation for clarity and accuracy
- [ ] Verify all internal links work correctly
- [ ] Confirm consistent terminology throughout

---------

Co-authored-by: Alex Krawiec <[email protected]>

Author: gaprl

docs/product/crons/job-monitoring.mdx

@@ -48,8 +48,14 @@ your monitor alert.
 
 Cron monitors can be assigned an owner as either a Team or specific Organization Member. When an owner is assigned to a monitor, new issues produced by failures of that monitor will be assigned to that owner.
 
+Monitor owners also receive notifications when a monitor becomes broken. Learn more about [broken monitor notifications](/product/crons/troubleshooting/#why-was-my-monitor-environment-marked-as-broken-or-automatically-muted).
+
 ## Pausing Your Cron Monitor
 
 You can pause job monitoring in the header of your cron monitor. When you pause, your monitor will stop recording check-ins and will no longer notify you of any failed or missed check-ins.
 
 Note: Pausing your cron monitor won't pause the execution of your job or change the configuration of your job scheduler.
+
+### Automatic Muting
+
+If a monitor environment has been consistently broken for an extended period, Sentry may automatically mute it to reduce notification noise. Unlike pausing, muting does not stop billing. Learn more about [automatic muting and broken monitors](/product/crons/troubleshooting/#why-was-my-monitor-environment-marked-as-broken-or-automatically-muted).

docs/product/crons/troubleshooting.mdx

@@ -12,7 +12,20 @@ All monitors are automatically deactivated at the start of a new billing period
 
 <Expandable title="Why Was My Monitor Environment Marked As Broken or Automatically Muted?">
 
-If your monitor environment has been in a failing state for 14 days or more, we will automatically mark it as broken and notify you of this escalated failure state via email. If the monitor environment stays in this state for another 14 days, we will automatically mute it to stop it from generating additional noise through notifications or issue events.
+If your monitor environment has been consistently broken for 14 days or more (with only missed, timed out, or failed check-ins), we will automatically mark it as broken and notify you of this escalated failure state via email.
+
+If the monitor environment continues to be broken after an additional 14 days, we will automatically mute it to stop it from generating additional noise through notifications or issue events.
+
+**Who Receives the Notification:**
+
+- If the monitor has an owner who is a user, that user will receive the email
+- If the monitor has an owner who is a team, all team members will receive the email
+- If the monitor has no owner, everyone in the project team will receive the email
+
+**Important Notes:**
+
+- You can disable these notifications in your [personal notification settings](/product/alerts/notifications/notification-settings/)
+- Muting a monitor does **not** stop billing. You will continue to be charged for muted monitors. To stop billing, you must deactivate or delete the monitor. See [Manage Your Cron Monitors](/pricing/quotas/manage-cron-monitors) for more details.
 
 </Expandable>