Fix denied or unavailable push notifications
Browser permissions, unsupported installation mode, and retrying after a backend error. Core.
Overview
Browser permissions, unsupported installation mode, and retrying after a backend error. Core. Use this guide to isolate the cause safely before repeating the action. Account preferences belong to you, while organization membership controls which shared workspaces and data you can access.
Identify the symptom
Browser permissions, unsupported installation mode, and retrying after a backend error. Core. Note the exact point where the actual behavior differs from what you expected.
Do not repeatedly submit, delete, publish, reconnect, or purchase while the result is uncertain. First verify whether the previous action completed in another tab, activity list, Audit Log, or external platform.
Checks to make in order
Start in My Settings or the account dashboard. Keep the affected item open where possible so you can compare the state after each check.
- Check 1: Browser permissions
Review browser permissions and choose the value that matches your intended result.
- Check 2: Unsupported installation mode
Review unsupported installation mode and choose the value that matches your intended result.
- Check 3: Retrying after a backend error
Review retrying after a backend error and choose the value that matches your intended result.
- Check 4: Core
Review core and choose the value that matches your intended result.
Safe recovery
After correcting the cause, refresh the page and repeat the smallest safe action that can prove the workflow works. The issue is resolved when your account or membership state shows the intended change.
If a retry could publish, delete, charge, revoke access, retire a public address, or send a message twice, contact an owner or support instead of guessing.
- Confirm that you are signed in with the email address that received the invitation or owns the setting.
- Check whether the invitation is still pending and has not expired.
- For organization-level access, ask an owner to review your membership and assigned role.
If you still need help
Send support the organization name, route, affected item ID, timestamp and timezone, exact message, screenshot, and reproducible steps. Include the relevant System Status or Audit Log entry when available.
Never send passwords, verification codes, cookies, access tokens, API keys, payment details, or other secrets.
Availability and access
This feature does not require an add-on, although permissions or organization settings may still apply.