# Troubleshooting

## Troubleshoot common issues with cron monitoring.

Why Were All My Monitors Disabled?

All monitors are automatically deactivated at the start of a new billing period if there's not enough [on-demand spend](/pricing/#on-demand-capacity) to cover all active monitors. Monitors can be manually activated based on on-demand availability. See [Manage Your Cron Monitors](/pricing/quotas/manage-cron-monitors/) for more details.

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.

Why aren't recurring job errors showing up on my monitor details page?

You may not have [linked errors to your monitor](/product/crons/getting-started/http/#connecting-errors-to-cron-monitors).

Why am I not receiving alerts when my monitor fails?

You may not have [set up alerts for your monitor](/product/crons/getting-started/http/#alerts).

What is the crons data retention policy for check-ins?

Our current data retention policy is 90 days.

Do you support a monitor schedule with a six-field crontab expression?

Currently, we only support crontab expressions with five fields.
