Statuses
What each attempt status means, what the browser reports back, and why accepted is not the same as seen.
Every notification creates one attempt per connected browser, and each attempt has its own status. There is no delivered status, because no browser vendor's push service reports delivery to a screen.
Warning
accepted means the push service took the message. It does not mean the notification was displayed: the device may be off, offline past the TTL, muted or in Do Not Disturb.Attempt statuses#
| Status | Final | Meaning |
|---|---|---|
| queued | not yet | Created and waiting for the sender, or waiting again after a retryable answer: a network failure, a timeout, 429, 5xx or any other status that is not an acceptance, 404/410 or 400/403/413. |
| processing | not yet | Being sent to the push service right now. A sender holds it for 60 seconds; if the sender stops, the attempt is picked up again. |
| accepted | final | The push service accepted the message for that browser. With a test key the attempt is set to accepted the moment it is created, and nothing is sent. |
| failed | final | The push service rejected the message for good (400, 403 or 413), the last of the 6 tries of a send job got a retryable answer, or the request could not be built. |
| expired | final | The TTL passed before Push could hand the message over, or its content had already been removed. A ttl of 0 gets 300 seconds. |
| invalid_subscription | final | The push service answered 404 or 410 (the browser is gone), or the browser was disconnected before sending. The browser is disconnected, and for a live send the attempt is removed from the month's count. |
Events reported by the browser#
Push's service worker reports what the person does with a notification. These fields are certain when present, and only the first event of each kind is kept.
| Field | Meaning |
|---|---|
| clickedAt | When the person first clicked the notification or one of its action buttons. |
| actionClicked | The id of the action button behind that first click, or null for a click on the notification itself. See actions. |
| closedAt | When the person first dismissed the notification without clicking it. |
NoteAn event is recorded only if it reaches Push. A missing
clickedAt does not prove nobody looked: the person may have read it and moved on, or the browser may have been offline.Lifecycle#
⫻
lifecycle
- Every
liveattempt starts asqueued, moves toprocessingwhen a sender picks it up, and ends in exactly one final status. - A retryable answer sends a
processingattempt back toqueuedfor another try, up to 6 tries per send job with growing waits. An attempt stuck for more than 15 minutes is queued again by the hourly cleanup with a fresh budget, until its TTL runs out. See what happens next. - A final status never changes again. Clicks and dismissals are added on top of
acceptedattempts.
Reading statuses#
Read a notification and all its attempts with its id:
⫻
curl
⫻
200 OK
- Most attempts settle within seconds. If you poll, a few seconds apart is enough, and stop once every attempt has a final status.
- Polling counts toward your rate limits.
- The dashboard shows the same attempts for each notification, with the last error the push service returned.