--- title: Issue States in Error Tracking description: >- Understand and manage error issue states in Error Tracking to organize, prioritize, and track the resolution of application issues. breadcrumbs: >- Docs > RUM & Session Replay > Error Tracking for Web and Mobile Applications > Issue States in Error Tracking --- > For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt). # Issue States in Error Tracking ## Overview{% #overview %} All issues in Error Tracking have a status to help you triage and prioritize issues or dismiss noise. There are five statuses: - FOR REVIEW: New or regressed issues that need attention. - REVIEWED: Triaged issues that need to be fixed, now or later. - RESOLVED: Issues that have been fixed and are no longer occurring. - IGNORED: Issues that require no further investigation or action. You can also snooze an issue to ignore it until a condition is met. - EXCLUDED: Issues that require no further investigation, stops collecting new errors, and no longer count towards usage or billing All issues start with a FOR REVIEW status. Error Tracking automatically updates the status in the cases described below, or you can manually update the status. You can also view the history of a given error's state changes. The diagram below shows how the Error Tracking states are updated automatically and manually: {% image source="https://docs.dd-static.net/images/error_tracking/issue-states-diagram.5fffeb362efc2ceb4ab98070c5c295b2.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/error_tracking/issue-states-diagram.5fffeb362efc2ceb4ab98070c5c295b2.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Error Tracking Issue States" /%} ## Automatic review{% #automatic-review %} Error Tracking automatically marks issues as REVIEWED if one of the following actions has been taken: - The issue has been assigned - A work item has been created from the issue {% image source="https://docs.dd-static.net/images/error_tracking/auto-review-actions-2.724e53c17d92445c58bb9b25a6d4dc85.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/error_tracking/auto-review-actions-2.724e53c17d92445c58bb9b25a6d4dc85.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Error Tracking automatic review actions" /%} ## Automatic resolution{% #automatic-resolution %} Error Tracking automatically marks issues as RESOLVED that appear to be inactive or resolved due to a lack of recent error occurrences: - If the issue was last reported in a version that is more than 14 days old, and a newer version has been released but does not report the same error, Error Tracking automatically resolves the issue. Configure your services with version tags (see instructions for [APM](https://docs.datadoghq.com/tracing/services/deployment_tracking.md), [RUM](https://docs.datadoghq.com/real_user_monitoring/guide/setup-rum-deployment-tracking.md?tab=npm), and [Logs](https://docs.datadoghq.com/getting_started/tagging/unified_service_tagging.md)) to ensure that automatic resolution accounts for versions of your services. - If `version` tags are not set up, Error Tracking automatically resolves an issue if there have been no new errors reported for that issue within the last 14 days. **Note**: The auto-resolution logic does not take `version` into account. ## Automatic re-opening through regression detection{% #automatic-re-opening-through-regression-detection %} See [Regression Detection](https://docs.datadoghq.com/error_tracking/regression_detection.md). ## Updating the issue status{% #updating-the-issue-status %} The issue status appears anywhere the issue can be viewed, such as in the issues list or on the details panel for a given issue. To manually update the status of an issue, click the status and choose a different one in the dropdown menu. {% image source="https://docs.dd-static.net/images/error_tracking/updating-issue-status.bfc2a7a35dcf0f75e1ac3353b05e0492.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/error_tracking/updating-issue-status.bfc2a7a35dcf0f75e1ac3353b05e0492.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Activity Timeline in the Error Tracking Issue" /%} ## Excluding an issue{% #excluding-an-issue %} The `EXCLUDED` status lets you prevent specific errors from being tracked, ensuring they are not collected or counted toward billing. This helps you remove non-actionable errors or issues caused by expected failures without needing complex exclusion rules. To exclude an issue, click its status and choose EXCLUDED in the dropdown menu. Excluded issues are still accessible in the IGNORED tab. You can review their history at any time. {% image source="https://docs.dd-static.net/images/error_tracking/issue-states-excluded.f471cbb29df20f0cef201a84d4bb2d19.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/error_tracking/issue-states-excluded.f471cbb29df20f0cef201a84d4bb2d19.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Excluded in issue status dropdown" /%} To resume collecting errors for an excluded issue, select any status other than EXCLUDED. ## Snoozing an issue{% #snoozing-an-issue %} Snoozing an issue moves it to IGNORED until a condition you define is met. When the condition is met, Error Tracking moves the issue back to FOR REVIEW. Use snoozing when you need more evidence before deciding whether to take action on an issue: the issue stays out of your inbox, but it comes back if its impact grows. For example, you can ignore an issue until it affects 10 distinct users. ### Snooze conditions{% #snooze-conditions %} You can snooze an issue until one of the following conditions is met: - **Occurrences**: The issue reaches a number of new error occurrences. - **Affected users**: The issue affects a number of distinct users. This condition requires errors to have the `@usr.id` attribute. - **Elapsed time**: A duration passes after you snooze the issue. Occurrences and affected users are counted from the moment you snooze the issue. Errors that occurred before the snooze do not count toward the condition. To combine multiple conditions, or to count distinct values of any error attribute (e.g. `@account.id`), use the [`update_datadog_error_tracking_issue`](https://docs.datadoghq.com/mcp_server/tools.md#update_datadog_error_tracking_issue) tool of the Datadog MCP Server. For example, you can ignore an issue until it affects 10 distinct users or a week passes, whichever comes first. This helps you clear your backlog while still catching the issues that become important. ### Snooze an issue{% #snooze-an-issue %} 1. Click the status of an issue in the issues list or on the issue details panel. 1. In the dropdown menu, hover over IGNORED. 1. Select one of the following options, then choose a value: - For… to snooze the issue for a duration. - Until this occurs again… to snooze the issue until it reaches a number of new occurrences. - Until this affects an additional… to snooze the issue until it affects a number of additional users. {% image source="https://docs.dd-static.net/images/error_tracking/issue-snooze.16d106b2ea1a6009e6caa2e52b645e1d.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/error_tracking/issue-snooze.16d106b2ea1a6009e6caa2e52b645e1d.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Snooze options" /%} Snoozed issues appear in the IGNORED tab. ### Cancel a snooze{% #cancel-a-snooze %} To cancel a snooze, manually change the status of the issue. Selecting any status, including IGNORED, cancels the active snooze and its conditions no longer apply. ## Issue history{% #issue-history %} View a history of your issue activity with the Activity Timeline. On the details panel of any Error Tracking issue, view the Activity Timeline by clicking the Activity tab. {% image source="https://docs.dd-static.net/images/error_tracking/issue-status-history-3.5e1569f80ed90a8811a5e405a4545a75.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/error_tracking/issue-status-history-3.5e1569f80ed90a8811a5e405a4545a75.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Activity Timeline in the Error Tracking Issue" /%} ## Further Reading{% #further-reading %} Additional helpful documentation, links, and articles: - [Regression Detection](https://docs.datadoghq.com/error_tracking/regression_detection.md)