Monitor with scheduled checks set to "never" ran again exactly one month later

I had a monitor that I wanted to stop using, but wasn’t ready to delete, so I set its scheduled interval to “never” which I assumed would mean it would essentially be disabled until I decided to re-enable it at a future date by setting a new schedule.

However, interestingly, exactly one month after I disabled the check, I received a notification about site changes even though the schedule for this monitor hadn’t been touched. Therefore I’m wondering if I stumbled upon a bug with the behavior of that “never” interval.

Here’s what the check log showed:

I found that timing suspect and figured I’d log the possible bug here.

@nirajsanghvi Thanks for raising this and for your patience while we looked into it.

You’re absolutely right in observing that the monitor still ran once, even after being set to “Never.” Internally, the “Never” setting currently behaves more like a very infrequent schedule (approximately once every 30 days), rather than fully disabling the monitor. This is a bit of legacy behavior — designed in part to help users catch potential issues (like broken monitors or inaccessible pages) even when checks are paused.

If you’d like to completely disable a monitor so it doesn’t run at all, we recommend turning it off entirely using the toggle next to the monitor in your Watchlist. This will ensure it doesn’t check unless manually reactivated.

We really appreciate you bringing this to our attention.

Hey Srijith, sorry for my delayed response, but I really appreciate the thorough explanation! What you described makes sense, though I think it should be made clearer somewhere that “never” does not actually mean never, since that feels very unexpected/unintuitive.

I had somehow completely missed that on/off toggle at the end of the row, and that definitely works for what I wanted to completely disable the monitor.

@nirajsanghvi Thanks for the follow-up, and no worries at all about the delayed response.

You’re absolutely right — the behavior of the “Never” schedule can be unintuitive, and we agree it should be made clearer that it doesn’t fully disable a monitor. Your feedback here is very helpful, and we’ll make sure it’s shared with the team so we can improve how this is communicated in the UI and documentation.

I’m glad the on/off toggle worked for your use case and gives you the control you were looking for to completely disable a monitor.

Thanks again for taking the time to flag this and for following up. If you have any other questions or suggestions, feel free to let us know — we really appreciate the feedback!