Notification delivery log

Use the delivery log to investigate outbound email and text messages. It records delivery processing, not whether a person read a message, acknowledged a memo or completed a task. In-app inbox items are separate and do not appear here.

Access needed

Access depends on your assigned permissions and workflow scope.

Read/filter outbound delivery history and inspect details: notifications.deliveries.read
Email and SMS only. This does not grant personal inbox access or delivery configuration.
Role and permission labels
Typical responsibility: Authorized notification investigator or administrator. Role names alone do not grant access.
Read outbound notification delivery history
Open Delivery settings: notifications.settings.manage
Separate read/write administration permission. Not required just to inspect the delivery log.
Role and permission labels
Typical responsibility: Authorized notification investigator or administrator. Role names alone do not grant access.
Manage notification delivery settings
Open View template: notifications.templates.manage
Separate template access. Delivery-history permission does not grant template changes.
Role and permission labels
Typical responsibility: Authorized notification investigator or administrator. Role names alone do not grant access.
Manage notification templates

Demo screenshots may show broader access than your account.

Open delivery history

Open Notifications → Delivery log. Review Created, Recipient, Channel, Status, Category, Attempts, Failure reason and Sent together. Recipient addresses are masked.

Six failed demo email entries with masked recipients — Read-only demo delivery history; no message was sent during this review.

The demo contains six failed email entries with EMAIL_NOT_CONFIGURED, zero attempts and no sent time. This is a delivery-configuration failure; it does not mean the related payroll, document or leave operation failed. The corresponding in-app notification can still be available.

Find a delivery

Choose channel and status
Open Filter records. Choose Email or text messages and the status relevant to your investigation.
Narrow the category and creation window
Filter Category and use From (UTC) and To (UTC) when needed. These date filters apply to creation time; displayed record times use your local timezone.
Review the scope
Check filter chips, sorting and pagination. Remove filters or Reset when the search is too narrow, then Refresh delivery log to reload the view.
Inspect the exact entry
Select View delivery. Compare its Delivery ID, template, provider details, attempts, failure reason and timestamps before deciding what needs attention.

Delivery log filters including UTC creation range — Read-only demo delivery history; no message was sent during this review.

Read delivery details

The detail panel identifies the recorded delivery and explains common failure reasons. Use Previous and Next record to compare entries on the current page. Keep the Delivery ID when asking an authorized administrator to investigate.

Email delivery details explaining EMAIL_NOT_CONFIGURED — Read-only demo delivery history; no message was sent during this review.

A masked recipient is intentionally incomplete. Do not guess the full address from the log or treat two similar masks as proof they are the same person. Message content is removed when delivery processing reaches a final state; this log is not an archive of notification bodies.

Understand the statuses

Status	Meaning	What to check
Pending	Queued and waiting for its next attempt.	Next attempt time and whether processing is progressing.
Sending	Claimed by the delivery worker for processing.	Refresh later; a temporary worker lease is not a recipient receipt.
Sent	Accepted by the provider.	This does not establish inbox arrival or reading.
Failed	Final failure with a recorded reason.	Investigate the reason and relevant configuration.

Some failures occur before a message can be queued. Zero attempts with EMAIL_NOT_CONFIGURED is therefore meaningful; it does not mean the log failed to load an attempt count.

Interpret common failure reasons

Failure reason	What it means and who should investigate
EMAIL_NOT_CONFIGURED	No workspace or platform email provider is configured. Ask an administrator with delivery-settings access.
RECIPIENT_INVALID	The address or number is invalid. Verify the destination through its authorized account or employee workflow.
TEMPLATE_NOT_FOUND or TEMPLATE_INVALID	The selected template is missing or cannot render. Ask an authorized template administrator.
PROVIDER_REJECTED	The provider refused the message; this failure is not automatically retried.
PROVIDER_UNREACHABLE or DISPATCH_ERROR	A temporary failure can return to Pending for an automatic retry.

Temporary failures are documented to retry up to five attempts, with delays starting at 30 seconds, doubling and capped at 30 minutes. Inspect Next attempt rather than assuming every failure will retry. The live demo entries are configuration failures, not a verified temporary-retry example.

Delivery settings opens separate email/SMS configuration when you have the required access. View template opens template administration when available to your account. Delivery-log access grants neither configuration changes nor template editing.

For personal channel choices, see Notifications and preferences. Preferences do not configure providers, and disabling a personal optional channel is not a repair for an invalid provider setup.

Troubleshooting

Problem	What to check
An in-app item is absent from this log	The log covers outbound email and SMS only.
Delivery settings is unavailable	Configuration requires notifications.settings.manage separately.
A final failure does not retry	Only documented temporary failure types retry automatically; final states remain final.
A Sent message was not seen by the person	Provider acceptance is not a reading receipt; verify through appropriate support channels.
No entry appears	Check category/channel/date filters, pagination and whether that channel was requested.
The message body is unavailable	Final delivery content is removed; inspect source records within your access.

What was verified

The populated six-entry failed-email list, filter menu and EMAIL_NOT_CONFIGURED detail were inspected in light theme. No provider setting, destination, template or delivery was changed and no test message was sent. Sent/SMS processing and retry timing were not tested.