[GH-ISSUE #49] Checks move to "pause" state but receive their ping normally #25

New issue

Closed

opened 2026-02-25 23:40:49 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 23:40:49 +03:00

Owner

Originally created by @danielsteigpayleven on GitHub (Mar 18, 2016).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/49

Hi,
we are seeing quite a lot of checks in a pause state but we have no idea, how the pause state is defined and what it means. (Isn't mentioned in the docs) The checks get their ping regularly though.

Thanks for the help in advance.

best regards,

Daniel

Originally created by @danielsteigpayleven on GitHub (Mar 18, 2016). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/49 Hi, we are seeing quite a lot of checks in a pause state but we have no idea, how the pause state is defined and what it means. (Isn't mentioned in the docs) The checks get their ping regularly though. Thanks for the help in advance. best regards, Daniel

kerem closed this issue

2026-02-25 23:40:49 +03:00

kerem commented

2026-02-25 23:40:50 +03:00

Author

Owner

@cuu508 commented on GitHub (Mar 18, 2016):

Do you see this on healthchecks.io or your own deployment?
If it's on your deployment, is your codebase maybe behind master?

The "paused" state was used to disable checks when notification fails for any reason. Otherwise the notification would be retried and could potentially flood recipients with tons of emails. I've since changed this logic, and the "paused" state isn't used any more.

@cuu508 commented on GitHub (Mar 18, 2016): Do you see this on healthchecks.io or your own deployment? If it's on your deployment, is your codebase maybe behind master? The "paused" state was used to disable checks when notification fails for any reason. Otherwise the notification would be retried and could potentially flood recipients with tons of emails. I've since changed this logic, and the "paused" state isn't used any more.

kerem commented

2026-02-25 23:40:50 +03:00

Author

Owner

@danielsteigpayleven commented on GitHub (Mar 18, 2016):

We are selfhosting it. Ah, then we are going to update next week and i let you know if this happens again.

Thanks for the quick update,

Daniel

@danielsteigpayleven commented on GitHub (Mar 18, 2016): We are selfhosting it. Ah, then we are going to update next week and i let you know if this happens again. Thanks for the quick update, Daniel

kerem commented

2026-02-25 23:40:50 +03:00

Author

Owner

@cuu508 commented on GitHub (Apr 5, 2016):

Hello @danielsteigpayleven – I'm assuming this has been resolved and we can close the issue?

@cuu508 commented on GitHub (Apr 5, 2016): Hello @danielsteigpayleven – I'm assuming this has been resolved and we can close the issue?

kerem referenced this issue

2026-02-25 23:43:58 +03:00

[PR #25] [CLOSED] n_pings is unnecessary #866