Delivery history
See which notifications were sent, which were not, and why.
Tracemill records every notification it queues for a recipient — whether it was sent or not, and why — and keeps the record for 90 days.
Changes that never become a notification have no entry: classes set to Off, empty digests, and changes dropped because their target was snoozed when Tracemill processed them.
Where to find it
- Your email — Recent deliveries at the bottom of Workspace → Notifications lists the notifications addressed to you, newest first. Every member sees their own.
- A destination — Deliveries on the destination's row under Workspace → Destinations. Every member can see it. Deleting a destination deletes its history.
Each entry shows what was sent (Alert, Digest, Report, or Test message), the channel (Email, Slack, or Microsoft Teams), its status, and when.
Statuses
| Status | Meaning |
|---|---|
| Queued | Waiting to be sent, or waiting to retry after a temporary failure |
| Sending | Being sent now |
| Sent | Accepted by the mail service or the chat webhook |
| Failed | Tracemill tried and could not deliver it |
| Not sent | Tracemill decided not to send it; the reason says why |
Temporary failures — timeouts, rate limits, server errors — are retried with increasing delays before a message is marked Failed.
Delivery is at least once: in rare cases, such as a restart at the moment a message is handed over, a recipient may get the same message twice.
Reasons
| Reason | What happened | What to do |
|---|---|---|
| email address not verified | Your address is not verified | Sign in so that your address is confirmed |
| email address bounced or reported spam | Your address is suppressed | Fix the mailbox, then Resume email |
| no longer a workspace member | The recipient left the workspace before it was sent | — |
| target snoozed | The target was snoozed before the alert went out | — |
| target archived | The target was archived before the alert went out | — |
| workspace daily send limit reached | The workspace hit its daily limit for the channel | See below |
| destination turned off | The destination was turned off by an admin or after failed deliveries | Turn it back on |
| destination deleted | The destination was deleted before it was sent | — |
| the channel refused it | The mail service or webhook rejected the message permanently | Check the webhook or mailbox |
| every retry failed | Temporary failures continued through every retry | Check the webhook; later messages are tried again |
| the message could not be built | An error on Tracemill's side | Contact support |
Daily send limits
To protect your inboxes and channels from a runaway volume of messages, each workspace can send at most this many notifications per day:
| Channel | Limit per workspace per day |
|---|---|
| 1,000 | |
| Slack | 500 |
| Microsoft Teams | 500 |
Days are counted in UTC. Once a limit is reached, further messages on that channel are recorded as Not sent: workspace daily send limit reached and are not sent later; sending resumes at 00:00 UTC. A message counts once Tracemill starts sending it, even if it then fails or is not sent in the end; messages held back earlier for another reason do not count. The test message posted when you add a destination does not count; Send test does.
If you reach a limit, prefer digests over immediate alerts for the noisiest classes or targets.