Errors Digests
Digests deliver scheduled roundups of your most important Errors directly to your team via email, Slack, Teams, and webhooks.
Renamed from Issues DigestsDigests now operate over your Errors and are configured from the Errors view. Their behavior is unchanged from the previous Issues Digests — only the name and location have moved.
LogRocket delivers a daily or weekly Errors Digest to your Slack channel, Microsoft Teams channel, email address, or webhook endpoint of choice. The digest summarizes your app's most severe Errors from the period. Weekly digests are delivered Monday mornings, ET.
To set one up, go to the Errors view, click Configure Digests in the top-right corner, and open the Digests tab. This feature is available on Pro and Enterprise plans only.
Digests, severity, and Galileo AIErrors Digests are driven by severity, generated by LogRocket's Galileo AI. If an Error's related Issue has a Galileo-generated analysis, that summary is included in the digest.
Configuring digests
Errors Digests can be configured with the following conditions:
- Delivery schedule — Daily or Weekly. Weekly digests are sent Monday mornings, ET.
- Error types — We recommend including all types, but you can scope a digest to specific ones, such as JS Errors and Network Errors.
- Page Definitions — Scope a digest to certain Visited URL Definitions, or feature areas of your app.
- First Seen — Limit the digest to Errors newly detected within the selected schedule, or leave the filter off.
- Severity — Include only Galileo-recommended severe Errors, or choose "Any Severity" to include all.
Digest destinations
Digests can be sent to Slack, Microsoft Teams, email, and webhooks. When creating a digest, choose the Send to destination.
Digests via email
Select Email in the "Send to" field and add a single recipient address. To reach several people, either set up an alias address with your email administrator (for example, [email protected]) or create one email digest per recipient.
Digests via Slack
Select Slack in the "Send to" field, then click Connect Slack to complete Slack's authentication and setup flow.
Digests via webhook
Select Webhook in the "Send to" field and paste your destination's endpoint URL into the Webhook URL field.
Example webhook payload
{
"type": "ErrorsDigest",
"appID": "orgID/projectID",
"title": "Severe Errors Weekly Digest",
"startDate": "2026-07-06T16:25:48",
"endDate": "2026-07-13T16:25:48",
"url": "https://app.logrocket.com/orgID/projectID/errors?...",
"totalErrors": 18,
"topErrors": [
{
"errorType": "JS Error",
"url": "https://app.logrocket.com/orgID/projectID/error/...",
"sessionCount": 153,
"label": "JS Error • Error Can't find element with id embedded-lock",
"screenshot": "https://app.logrocket.com/screenshots/...",
"analysisSummary": "There is a missing element...",
"analysis": {
"isSevere": true,
"userImpact": "Brief statement of user impact",
"reproductionSteps": "List of steps to reproduce",
"nextSteps": "What to look at next",
"analysis": "Full analysis. Markdown with [session links](https://example.com)."
}
},
{
"errorType": "Network Error",
"url": "https://app.logrocket.com/orgID/projectID/error/...",
"sessionCount": 13,
"label": "Network Error • 502 POST app.company.com/v1/",
"screenshot": "https://app.logrocket.com/screenshots/...",
"analysisSummary": "Users experience 'Bad Gateway' errors...",
"analysis": {
"isSevere": true,
"userImpact": "Brief statement of user impact",
"reproductionSteps": "List of steps to reproduce",
"nextSteps": "What to look at next",
"analysis": "Full analysis. Markdown with [session links](https://example.com)."
}
},
{
"errorType": "Dead Click",
"url": "https://app.logrocket.com/orgID/projectID/error/...",
"sessionCount": 498,
"label": "Dead Click • on text 'Complete Checkout'",
"screenshot": "https://app.logrocket.com/screenshots/...",
"analysisSummary": null,
"analysis": null
}
]
}
Author note: confirm the exact webhooktypestring and field names post-migration. The current live payload usesIssuesDigest/topIssues/issueType. This draft renames them toErrorsDigest/topErrors/errorTypeto match the rename, but the engineering team may keep the legacy keys for backward compatibility — verify before publishing.
Digests via Microsoft Teams
Select Microsoft Teams in the "Send to" field and follow the setup instructions to connect the digest to your Teams channel. Paste the webhook URL Teams provides into the configuration view and click Save. Your first digest arrives the following Monday morning.
Updated about 4 hours ago

