Notes and Schedule
Read reminder status and retry delivery
Understand reminder counts, delivery health, retry limits, and missing device alerts.
A reminder's status describes its saved delivery or control state. It does not prove that someone saw an alert or completed the work.
Check the current status
- Open the owning workspace's Schedule and find the date.
- Open the work's details and read the reminder badge and explanation.
- Check the due or action time and any failure reason.
- Follow the appropriate recovery below; use Retry only when it is offered.
- Refresh the details after an action and check the resulting state.
The Reminders total counts pending, failed, and snoozed reminders on items in the current filtered view. It is not an account-wide unread count.
| Status | Meaning |
|---|---|
| No reminders queued | No counted active, delivered, or acknowledged reminder is shown for the date; future recurrence reminders may not yet be prepared. |
| Pending | A reminder is waiting. Its due time may already have passed; this is not proof of device delivery. |
| Snoozed | A later reminder time was saved. See the local-alert limitation. |
| Acknowledged | Someone acknowledged the shared reminder. The work may still be incomplete. |
| Delivered | The delivery path reported success. This is not a read receipt or a completion record. |
| Canceled or Reminder skipped | The reminder was settled because its source or occurrence changed. |
Local device alerts do not update the server reminder to Delivered simply because the device displayed them. A Pending badge can therefore remain after a local alert. A date can also retain multiple reminders after timing changes; its badge describes the latest one, while an available action can apply to another eligible reminder.
Retry a failure
For an eligible Retryable failure, select Retry, or Actions > Retry reminder. Wait for the result. Automatic and manual delivery attempts share a limit of three total attempts. The failure label can remain after the Retry action is no longer available.
Retry is not offered for Permission denied, Subscription expired, Subscription revoked, Target unavailable, Provider disabled, or Adapter unavailable. Restore content access or reconnect the affected notification destination as appropriate. Provider or adapter problems require administrator help. Repairing setup does not itself replay every old reminder.
If Retry reports that delivery is already being processed or no longer retryable, refresh before trying again. Device-local reminders are not sent by the server Retry control.
No alert arrived
Check notification setup, the loaded workspace and date range, and whether the reminder time had already passed. Browser/mobile push enrollment alone does not route ordinary scheduled reminders through push. Use Home or Schedule to launch the work while resolving delivery.