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 to cover all active monitors. Monitors can be manually activated based on on-demand availability. See Manage Your Cron Monitors for more details.

Why Was My Monitor Environment Marked As Broken or Automatically Muted?

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:

Why aren't recurring job errors showing up on my monitor details page?
Why am I not receiving alerts when my monitor fails?
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.

Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").