Why didn't it page me?

Check these in order. Each one is visible to you, and the alert's timeline records everything we tried.

1. Did the alert arrive at all?

Open Alerts. If it is not there, we never received it. The problem is between your monitoring and us, not inside Acked.

Check what your sender got back. A 401 means the key or token is wrong or revoked. A 400 means the signal was malformed, and the response body says how. Anything in the 2xx range means we have it, including 202 buffered.

2. Was it deduplicated onto an existing alert?

This is the most common surprise. If an alert with the same event_key is already open on that service, your new signal joins it rather than opening another, and nobody is paged again, because somebody was already told.

Look for an open alert with a count above one. If separate occurrences should page separately, they need different event_keys. See Sending alerts.

3. Was anyone on call?

Open the service, then its schedule, and look at who is on call right now. Two things catch people out:

• Timezone. A schedule's hours are in the schedule's timezone, not yours and not the alert's.
• An override. An override replaces the rotation for its window. If one is active, that person is on call and the rotation is not.

If the alert reached unreachable, we paged every level, the chain repeated, and nobody acknowledged. That is a schedule problem, not a delivery one.

4. What did we actually try?

Open the alert. Its timeline lists every delivery attempt: the channel, who it went to, and whether it succeeded. This is where you find out whether the problem is ours or the device's.

• No attempts at all. Nobody was resolved as on call. Back to step 3.
• Attempts recorded as failed. We tried and the provider refused. If it is push, the device token is usually stale, and opening the app re-registers it.
• Attempts recorded as sent. It left us. Step 5.

5. It says sent, and my phone was silent

Then it reached Apple or Google and the handset made the decision. In order of likelihood:

• Notifications are not allowed. Check the app's notification permission. Being signed in is not the same as being allowed to notify you.
• A focus mode or Do Not Disturb. Only alerts we send as high urgency can break through, and only if you allowed critical alerts when the app asked.
• You were signed out on that device. Sign in again. A device only receives while its registration is live.
• The call went to voicemail. On a plan with voice we call from +1-571-240-1029. Save it as a contact — an unknown number is what silence-unknown-callers and most spam filters act on first. Download the contact card.

6. It arrived, late

Compare the alert's created time with the first attempt on its timeline. A first page goes out within seconds. Reminders for an unacknowledged alert repeat on a slower cadence by design, so a reminder arriving a minute or two after you expected it is normal. A first page doing that is not.

Still wrong?

support@acked.dev, with the alert id. It looks like 01H… and is on the alert page. It lets us read the same timeline you are looking at.