Push notification token reset: pre-release and first 30 minutes checklists

A change invalidates device tokens and notifications stop.

The pre-release checklist maps each item to a test class from the incident page. The first-30-minutes checklist covers detection, containment, the rollback decision and customer communication.

8 pre-release items · 8 first-30-minutes items · verified 2026-10-21

Pre-release checklist

PR-01Send a test push through the new push backend for two apps that share one p8 push configuration and confirm both apps' valid device tokens are accepted. integration
PR-02Send to the same device tokens through the old and new push backend versions and fail the test on any device-token-not-for-topic error from the new version. integration
PR-03Post a changed push token for an already enrolled device to the backend and confirm it replaces the stored token without a new enrolment. integration
PR-04Enrol an Android device on the previous app version, update it to the new version and confirm a push-to-accept login still succeeds. e2e
PR-05After the same app update, approve a symbol-to-accept login and confirm the user is logged in. e2e
PR-06Force a push token change on an enrolled Android device and confirm the app shows an error telling the user to re-enrol. e2e
PR-07Alert on any device-token-not-for-topic error in canary push sends, regardless of total send volume. canary
PR-08Compare the hourly bounce rate of canary and baseline push sends during a phased rollout and halt it when the canary rate is higher. canary

First 30 minutes

FM-01Read push send results for bounces and device-token-not-for-topic errors, grouped by app and push configuration type.
FM-02Match the start of the bounces to the latest push backend deployment or app store release.
FM-03Stop the phased rollout and revert to the previous push backend version.
FM-04If an app update changed device tokens, check whether the backend can accept the new token before asking users to re-enrol.
FM-05List the campaigns and automations whose notifications bounced during the rollout and decide whether to resend them.
FM-06Tell affected app owners which push configuration type failed and which channels kept working.
FM-07Give affected Android users the steps to re-enrol their devices for push-to-accept login.
FM-08Post a status update that names the platform, the affected notification types and the time window of failed sends.

Download the checklist

Pre-release checklist (Markdown)1.7 KB · v1.0.0
First 30 minutes checklist (Markdown)1.2 KB · v1.0.0

Only in this checklist

Every test class in this checklist also appears in at least one sibling checklist in the group; the item texts differ: Send a test push through the new push backend for two apps that share one p8 push configuration and confirm both apps' valid device tokens are accepted.

Questions

What should be checked before a release to prevent Push notification token reset?

8 pre-release items, PR-01 to PR-08. PR-01: Send a test push through the new push backend for two apps that share one p8 push configuration and confirm both apps' valid device tokens are accepted.

Is there a rollback plan for Push notification token reset?

The first-30-minutes checklist has 8 items. FM-01: Read push send results for bounces and device-token-not-for-topic errors, grouped by app and push configuration type.

What should a team do in the first 30 minutes after Push notification token reset is detected?

The first-30-minutes checklist has 8 items. FM-01: Read push send results for bounces and device-token-not-for-topic errors, grouped by app and push configuration type.

Is a Push notification token reset checklist still needed if deployment is automated?

Yes. Automation runs the steps; the checklist names what the tests must cover: integration tests, end-to-end tests and canary and progressive delivery checks.

Which pipeline stages does the Push notification token reset checklist cover?

The pre-release items map to the pre-deploy and post-deploy stages.

In what formats can the Push notification token reset checklist be downloaded?

Both checklists download as Markdown files: /downloads/push-notification-token-reset-pre-release.md and /downloads/push-notification-token-reset-first-30-minutes.md, licensed CC BY 4.0.