Delivery Logs
The **Logs** tab in the Delivery dashboard shows the status of every email sent through Own Auth Delivery for the selected app.
Log Entry Fields
| Field | Description |
|---|---|
| Status | Whether the delivery event is accepted, delivered, or failed. |
| Type | Verification, magic link, password reset, or invitation. |
| Recipient | The email address used for delivery. |
| Timestamp | When that delivery event was recorded. |
| Error | A safe failure reason, shown only for failed events. |
Statuses
| Status | Meaning |
|---|---|
| Accepted | Delivery received the email request and queued it for sending. The email hasn't been delivered yet. |
| Delivered | The email was delivered to the recipient's mail server. This doesn't guarantee inbox placement. The mail server accepted it. |
| Failed | The email could not be delivered after all retry attempts. |
Error Messages
Failed entries show a sanitised error that is safe to display in the dashboard. Possible messages include:
- Mailbox full
- Invalid recipient
- Domain not found
- Connection timed out
- Email provider rate limited
- Email provider rejected the message
- Email send failed
Filtering
Select an app and open Logs. Filter by all statuses, accepted, delivered, or failed, and by the last 24 hours, 7 days, 30 days, or all time. The default view shows the last 7 days. Results are paginated 25 entries at a time.
Retries
Delivery retries temporary network and provider failures automatically. The default retry schedule is:
| Attempt | Default Delay |
|---|---|
| First retry | 30 seconds |
| Second retry | 2 minutes |
| Third retry | 10 minutes |
A provider Retry-After value can lengthen a delay up to 10 minutes. After the third retry fails, Delivery records a failed entry. Permanent provider failures, invalid recipients, and missing domains fail immediately without retrying.
What logs don't show
Logs never display:
- Auth tokens or links contained in the email
- Raw delivery keys
- Email body content
- Password reset URLs
This is intentional. Delivery logs are a debugging tool, not a security liability.