Help Center/Admin Operations/How to use the Failed Notifications screen (Notifications)
Admin Operations•Last updated: 2026-10-20•3 min read

How to use the Failed Notifications screen (Notifications)

Notification emails the provider refused, and delivery failures recorded when nothing could be queued.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

Sign in as an administrator and use Admin sidebar → Notifications → Failed Notifications, or go to /admin/notifications/failed. The heading reads "Failed Notifications".

2

Know where the data comes from

This page reads i8_email_outbox (failed, notification:*) and i8_notification_deliveries (FAILED). Columns: Source, Kind, Recipient, Status, Error, Attempts, Retry, When.

3

Retry an email

The check icon titled "Retry (re-queue the email)" puts a failed outbox email back in the email queue after confirmation. The banner confirms; delivery itself happens when the email engine processes the queue.

4

Non-retryable rows

Rows from the delivery log (for example "email engine not configured") cannot be retried; fix the cause and send again.

5

Use the shared controls

Use the shared controls: the search box ("Search records, hashes, DIDs...") filters rows by any text; "Status:" offers ALL, FAILED; "Page Size:" sets 10, 15, 25 or 50 rows; Refresh reloads; Export saves the rows currently loaded as a JSON file. The line "Data:" under the heading names the real source.

Expected Operational Outcome

Failed emails are visible and can be re-queued; other failures say why they cannot.

Troubleshooting & Failure Modes

Symptom: Error "Failed to load notifications/failed: HTTP 401" or "HTTP 403"
Likely Cause: The session is not signed in or does not hold an administrative role.
Resolution: Sign in again with an administrator account and click Refresh.

Was this guide helpful?

Help us refine our platform documentation