Troubleshooting
Troubleshoot missing notifications and reminders
Distinguish stale work, permission problems, enrollment failures, and device delivery limits.
A missing notification can be a schedule, account, enrollment, permission, or delivery problem. Use Home or Schedule to find and launch the work while you check notification delivery.
Confirm the work is current
- Sign in to the expected account and select the workspace containing the work.
- Check its current date and time in Home or Schedule.
- Look for rescheduling, completion, a skipped occurrence, or an inactive assignment.
- Confirm you can still open the content and see the person attached to it.
An old Guide notification can be rejected after its schedule, due time, assignment, access, or enrollment changes. It can also belong to another account. Open the current item instead of repeatedly selecting the old alert. Acknowledging a reminder does not itself complete the work.
Check permission and enrollment separately
Open Settings > Notifications > Reminder enrollment, then use Check setup again after changing browser or device settings.
| Result | Next step |
|---|---|
| Denied permission | Allow CareMap notifications in browser/site or operating-system settings, then check setup again. |
| Not requested | Select the available Enable action and answer the permission prompt. |
| Granted, but Not enrolled | Use Enable or Reconnect for a browser, or Enable mobile for an installed app. |
| Enrolled, but no alert | Check permission, service readiness, the current reminder, and device limits below. |
| Unavailable | Use a supported browser or installed-app capability; permission changes cannot add missing support. |
| Setup failed to load | Try again reloads setup. Repeat the intended enrollment action afterward if needed. |
Active browsers or Active mobile can count other destinations. Check This browser or This device for the one you are using. Native permission combines native capabilities and does not prove both push and local support.
Check service and device limits
Disabled, Missing config, or Missing public key needs administrator or support attention for that delivery service. Mock ready is simulated service readiness, not proof of real push delivery. Provider ready is also not a receipt from your device.
For browsers, check notification permission, the browser profile used to enroll, and whether site data or subscription state changed. For mobile push, use Send test in 5 seconds when offered and check for the actual alert.
Local reminders depend on work already prepared on the device. Refresh Home or Schedule after changes. Desktop local reminders require the app to remain running; quitting or restarting can lose pending alerts. Launch work from Home or Schedule when a desktop banner has no launch action. See installed-app reminders.
Recover and get help
Use the available Revoke action and enroll again when repairing a stale destination. Previously scheduled local alerts may persist; system notification settings can stop those immediately. Revoking one destination does not revoke every device.
Share the account/workspace, expected time, browser or app, enrollment labels, and Last delivery issue with support. Leave private care details, notification tokens, and full launch links out of ordinary support messages.