[GH-ISSUE #418] Successful Ping, then down alert prior to next scheduled check in. #311

New issue

Closed

opened 2026-02-25 23:41:59 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:41:59 +03:00

Owner

Originally created by @mgeorgy on GitHub (Aug 28, 2020).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/418

I have healthchecks running and all of the functionality is working, however I have daily scheduled check-ins (0 8 * * *) with a 1 hour grace, that ping at the appropriate time only to have an alert generated an hour later that the service is down. Attached are images of the cron configuration and the check-in logs.

What am I missing?

Originally created by @mgeorgy on GitHub (Aug 28, 2020). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/418 I have healthchecks running and all of the functionality is working, however I have daily scheduled check-ins (0 8 * * *) with a 1 hour grace, that ping at the appropriate time only to have an alert generated an hour later that the service is down. Attached are images of the cron configuration and the check-in logs. What am I missing? ![image](https://user-images.githubusercontent.com/1755116/91594894-a12cef00-e930-11ea-8313-d869b322f85f.png) ![image](https://user-images.githubusercontent.com/1755116/91594984-c1f54480-e930-11ea-9fce-6a86cff49392.png)

kerem closed this issue

2026-02-25 23:42:00 +03:00

kerem commented

2026-02-25 23:42:00 +03:00

Author

Owner

@cuu508 commented on GitHub (Aug 31, 2020):

This is often caused by a timezone mismatch (the server has has one timezone, Healthchecks is configured to use a different one).

Also, if you've recently changed timezone on your server – if the cron daemon was not restarted afterwards it might still be using the old timezone.

@cuu508 commented on GitHub (Aug 31, 2020): This is often caused by a timezone mismatch (the server has has one timezone, Healthchecks is configured to use a different one). Also, if you've recently changed timezone on your server – if the cron daemon was not restarted afterwards it might still be using the old timezone.

kerem commented

2026-02-25 23:42:00 +03:00

Author

Owner

@mgeorgy commented on GitHub (Sep 1, 2020):

That was it. Thank you @cuu508 .

@mgeorgy commented on GitHub (Sep 1, 2020): That was it. Thank you @cuu508 .

kerem referenced this issue

2026-02-25 23:44:10 +03:00

[PR #313] [MERGED] set/update the checks description through the API #928