Settings
Each option answers a different question.
| Setting | What it means in Issues | Default |
|---|---|---|
| New error groups | Email when a brand-new grouped issue appears in Issues. | On |
| Reopened error groups | Email when a group you had resolved, ignored, or archived gets a fresh occurrence and needs another look. | On |
| Lifetime count milestones | Email when one group's all-time occurrence count reaches a milestone, even if those events were spread out. | Off |
| Single-error volume threshold | Email when one grouped issue becomes noisy inside the recent window you choose. | Off, 25 events in 60 minutes |
Do not confuse the thresholds
Milestones answer "has this one issue become important over its whole life?" The single-error threshold answers "is this one issue suddenly noisy right now?" Project-wide spike alerts live on the Project health page because they count the whole project, not one group.
Connected request context · Logister 3.8+
Inspect related evidence from an error email.
When related requests are enabled and an app/backend connection matches the occurrence's environment, existing first-error and grouped-alert emails can include up to five related records. Logister checks the recipient's project access when building the message; the connection itself grants no permissions.
These records provide request and release context, not proof of root cause. They do not merge issues, suppress duplicate alerts or change notification eligibility. New deliveries recheck access; already delivered emails cannot be recalled. See connected evidence and export limits.
Verify
Trigger the exact condition you enabled.
- For new group mail, create a test error that has not appeared before.
- For reopened group mail, mark the group resolved or ignored, then send the same grouped error again.
- For frequent-error mail, temporarily lower the count and window, then send repeated events for the same grouped issue.
Troubleshooting
Check grouping before checking email delivery.
| Symptom | What to check |
|---|---|
| No new-group email | The event may have grouped into an existing issue. Use a unique fingerprint or message for the test. |
| No reopened email | The group may still be unresolved, or the new occurrence may not share the same grouping fingerprint. |
| No frequent-error email | The repeated events may not have crossed the configured count inside the configured window. |
| The wrong person receives mail | Notification preferences are per user and per project; check the recipient's own Settings › Notifications. |
Use notification setup requirements after Issues shows the alert condition happened.