Clean up notification registrations

Global administrators use Admin → Dashboard → Maintenance → Notifications to maintain stale notification registrations across accounts.

These actions affect delivery destinations. They do not delete accounts, Guides, schedules, or past Reports.

Preview revocation

1. Open the Notifications card.
2. Select Dry Run.
3. Wait for Checking to finish.
4. Read Notification cleanup dry run, counts, reasons, and cutoffs.
5. Decide whether the proposed revocations fit the problem being addressed.

Dry Run previews revocation, not deletion. Its revoked count is the number proposed for revocation; no registration is changed by that preview.

Apply the appropriate cleanup

1. Select Revoke Stale to disable eligible active registrations, or Delete Revoked to remove sufficiently old revoked registrations.
2. Wait for Revoking or Deleting to finish.
3. Read Notification cleanup applied, the action, counts, and cutoffs.
4. Confirm the result before deciding whether another action is needed.

Both actions start immediately without a confirmation dialog. A dry run is optional. Each action evaluates current records, so its result can differ from an earlier preview.

Understand eligibility

With the dashboard's default request:

• Revoke Stale can revoke active registrations that expired, accumulated at least five recorded failures, or have a failure classified as provider rejection.
• Delete Revoked removes registrations revoked at least 30 days ago. It preserves active registrations and more recently revoked ones.
• Registrations that do not qualify for the chosen action are preserved.

Revoking prevents further delivery through that registration. It does not automatically turn off the operating system's notification permission. A person who needs that destination again must use the relevant notification settings to enroll it.

Delete Revoked is not a way to revoke an active destination immediately. There is no restoration control for deleted registration records here.

Read bounded results

Each dashboard request examines at most 50 candidate registrations, oldest updated first. Scanned is the number examined; eligible, revoked, deleted, and preserved describe classified candidates for that action.

One registration can contribute more than one reason. Reason totals therefore need not equal the number of registrations. Preserved is not a count of every healthy registration in the system.

There is no paging or filter control for this cleanup. Repeated runs can examine the same preserved candidates. Zero eligible does not prove that no eligible registrations exist beyond this batch; escalate persistent cleanup gaps rather than assuming repeated clicks will advance through everything.

An error can follow completed cleanup if a later dashboard read fails. Read the returned result; if the outcome is unclear, request support before repeating a mutation. Test checks one selected destination on your account and does not validate cleanup across everyone's devices.