Based on the knowledge sources provided, Elementary Data currently supports only two severity levels for tests: "error" and "warning" (also referred to as "warn"). This is because Elementary follows dbt's native test configuration approach, which only offers these two severity options. There isn't a built-in way to create additional categories like "Error - Triaged" or "Warning - Triaged" within the severity system itself. However, there are a few potential approaches you could consider: 1. Use the Incidents feature: Elementary Cloud has an incident management system that allows you to track the status of data issues. Each incident has status, assignee, and severity settings that could help you differentiate between new errors and ones being acted upon. [Incidents in Elementary](https://docs.elementary-data.com/features/alerts-and-incidents/incidents) explains how incidents work and how they can be managed. 2. Use tags: Several users in the Slack community have suggested using tags to differentiate between different types of tests when the severity options are limited. You could potentially tag tests that are being triaged with specific tags and then use those tags for filtering or routing alerts. [Send Slack Alerts](https://docs.elementary-data.com/quickstart/send-slack-alerts) mentions that you can use tags to send alerts to different channels. 3. Configure two separate tests: As suggested by a support staff member in one of the Slack threads, you could configure two separate tests - one with a different threshold or configuration than the other - to achieve more granular alerting. If you need more specific functionality, you might want to consider opening a feature request on the [Elementary GitHub repository](https://github.com/elementary-data/elementary/issues) as this seems to be a common request from users wanting more granular control over test categorization and alerting.

New message text here

Based on the knowledge sources provided, there's no indication that the

--suppression-interval

parameter can be used with the

edr send-report

command. The suppression interval feature is specifically designed for the

edr monitor

command to prevent sending multiple alerts for the same issue within a specified time period. As documented in the sources, this parameter is used as:

edr monitor --suppression-interval 24

The suppression interval is meant to act as a "snooze" period for alerts on the same issue, where Elementary won't send new alerts on the same issue that are generated within that interval [Alerts CLI flags](https://docs.elementary-data.com/oss/guides/alerts/alerts-configuration#alerts-cli-flags). The documentation doesn't mention this parameter being available for the

edr send-report

command. The

send-report

command is focused on generating and distributing the data observability report, while the suppression interval is specifically designed for controlling the frequency of alerts sent through the

monitor

command. If you're looking to control what appears in your reports, you might want to explore other options like using filters or selectors to customize the report content.