Settings
These emails are for project operations, not issue triage.
| Setting | Use it for | Default |
|---|---|---|
| Deployment summary emails | Email when a deploy is recorded so the team can connect later errors or latency changes to that release. | Off |
| Intake and quota warnings | Email when the project may be missing expected events or hitting limits that affect what appears in the UI. | On |
| Retention and archive failures | Email when cleanup or archive work fails so someone can fix it before old telemetry is removed. | On |
Related setup
Operational notices explain changes around the project.
Use these when someone should know about deploys, intake health, limits, or cleanup failures without watching every error group. If a deployment summary is missing, confirm the deployment appears for the project. If a retention notice is missing, confirm the Data tab has the retention or archive setting enabled.
Read deployment records or data retention next.
Verify
Trigger the operational event you want to hear about.
- For deployment summaries, enable the setting, send or record one deployment, then confirm it appears on the project Deployments page.
- For retention and archive failures, verify the Data tab has retention or archive settings enabled before expecting a notice.
- For intake and quota warnings, check the project has recent ingest activity and that the warning condition actually happened.
- If the project state is correct but no email arrives, use the setup requirements page to check project access, caps, quiet hours, SMTP, and Sidekiq.
Troubleshooting
Operational emails depend on the system that creates the event.
| Symptom | What to check |
|---|---|
| No deployment summary | The project may not have a stored deployment record, or deployment summary emails may still be off. |
| No retention failure notice | Confirm retention jobs ran, archive-before-delete or archive exports are enabled where expected, and a failure appears in Recent archive runs. |
| No intake warning | Check rate-limit responses, usage warning conditions, and project-level API traffic before changing email settings. |
| Operational mail arrives but triage mail does not | Operational notices and error triage alerts are separate preference paths. |