Not getting alerts?

If a monitor went down and you heard nothing, start on Notifications. Every destination shows what it is really doing, so you don’t have to guess. Work through the list below from the top.

What the Notifications page tells you

The header above your destinations counts only the ones that can receive an alert right now, for example 2 receiving · 1 need attention. It turns amber when none of them can.

Each row shows one of these:

What the row says	What it means	What to do
Connected	On, connected, covering at least one monitor, and no failed delivery is recorded.	Nothing.
Failing, with A delivery failed 4 min ago: …	CuliPulse tried to send an alert and the destination couldn’t deliver it. The reason is shown. A failure is recorded at most once an hour, so the time shown can be up to an hour behind the latest failure.	Fix the cause (see below), then press Send test alert. A successful test or alert clears the note.
Off	The switch is off, so nothing is sent here. In amber, CuliPulse turned it off for you (an email address that bounced, for example) and the row says why.	Switch it on, or fix the reason first.
Not receiving, with Specific, 0 monitors	The destination is set to specific monitors, but none are selected. Deleting the last monitor it covered has the same effect.	Open Alert scope… and pick at least one monitor, or choose All monitors.
Waiting…	You started connecting Telegram or Slack but didn’t finish. The row shows how long the link works.	Finish connecting, or remove the row.
Link expired	The Telegram link works for 15 minutes, and the Slack approval for 15 minutes too. It ran out before you finished.	Press Connect again to get a new link.

That note appears only after CuliPulse actually tried to send. A destination nobody has sent to yet can’t have failed, so after you change something on the other side, press Send test alert to check.

Common causes

A monitor you added later isn’t covered

A destination set to All monitors includes monitors you add later. A destination set to specific monitors does not: a new monitor stays uncovered until you add it to that destination.

On a monitor’s page, Alerts go to lists the destinations that will alert for it. If it shows No alerts will reach you for this monitor, open Notifications, choose Alert scope… on a destination, and add the monitor.

The destination is switched off or can’t receive

Email turned off from a link, a bounce or a spam report. See Why email alerts might be off.
Telegram stops when you press Stop or Block on the bot, or the bot is removed from a group. See If alerts stop arriving.
Slack stops when the CuliPulse app is removed from your workspace or the channel is deleted or archived. See Slack.
A webhook that answers with an error (a 4xx or 5xx status) or doesn’t answer in time. Check your endpoint’s logs. See Webhooks.

The monitor is paused, or not down yet

A paused monitor sends no alerts. Resume it from its page.
CuliPulse waits for a monitor to fail a few checks in a row before it alerts, so a single blip doesn’t wake you up. The alert arrives a little after the first failed check (the incident itself is dated from that first failed check). See Alerts & states.

Too many alerts went to email

Email is limited to 20 alerts an hour per account. Over that, email alerts pause until the next hour. Use another destination for anything that must not wait.

An alert failed and wasn’t sent again

If a destination keeps refusing an alert, CuliPulse stops trying for that alert. It is not saved up for later. Fix the destination and the next alert goes through. Use Send test alert to confirm.