[GH-ISSUE #38] unpausing checks that glitch out #17

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

Originally created by @diwu1989 on GitHub (Jan 29, 2016).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/38

image

Originally created by @diwu1989 on GitHub (Jan 29, 2016). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/38 ![image](https://cloud.githubusercontent.com/assets/380950/12670087/82f2d3ee-c61a-11e5-857b-1e49f7c6dc94.png)
kerem closed this issue 2026-02-25 23:40:47 +03:00
Author
Owner

@cuu508 commented on GitHub (Jan 29, 2016):

What I'm planning to do is to get rid of the "stopped" state.

Suppose you have multiple channels set up, let's say an email and a Slack webhook. And the webhook URL is obviously invalid, because of copy-pasting mishap.

What happens currently: the first time we try posting to Slack and fail, we mark the check as "paused" and give up forever. Even though the email channel might still be viable and useful.

What I think should happen: check never goes into "paused" state. If a posting to a channel fails, we store the most recent failure message and display it on "Channels" page, add a note about it in monthly report etc. Failures might also be temporary and it is worth retrying later.

<!-- gh-comment-id:176696332 --> @cuu508 commented on GitHub (Jan 29, 2016): What I'm planning to do is to get rid of the "stopped" state. Suppose you have multiple channels set up, let's say an email and a Slack webhook. And the webhook URL is obviously invalid, because of copy-pasting mishap. What happens currently: the first time we try posting to Slack and fail, we mark the check as "paused" and give up forever. Even though the email channel might still be viable and useful. What I think should happen: check never goes into "paused" state. If a posting to a channel fails, we store the most recent failure message and display it on "Channels" page, add a note about it in monthly report etc. Failures might also be temporary and it is worth retrying later.
Author
Owner

@diwu1989 commented on GitHub (Jan 29, 2016):

yeah deal that sounds way better, i hit a hiccup with slack recently and some of my checks got paused

<!-- gh-comment-id:177017087 --> @diwu1989 commented on GitHub (Jan 29, 2016): yeah deal that sounds way better, i hit a hiccup with slack recently and some of my checks got paused
Author
Owner

@cuu508 commented on GitHub (Jan 31, 2016):

This is now implemented: checks don't go into "paused" state. If there is a problem with one of the channels, it will be indicated on "Integrations" page, but rest of the channels still work.

<!-- gh-comment-id:177597746 --> @cuu508 commented on GitHub (Jan 31, 2016): This is now implemented: checks don't go into "paused" state. If there is a problem with one of the channels, it will be indicated on "Integrations" page, but rest of the channels still work.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#17
No description provided.