Based on the available knowledge sources, Elementary does not provide a built-in feature to route alerts for test query failures (i.e., when a test query fails to run and therefore produces no test failures) to a different Slack channel than regular test failures. The current alert routing is primarily based on model/test configuration, tags, or selectors, and there is no explicit mention of handling technical test execution errors separately from business/data test failures. You can configure custom channels for models and tests using the

meta

field in your dbt project, and you can use selectors to route alerts for specific tags or statuses to different channels by running multiple

edr monitor

commands. However, there is no documented way to distinguish and route only technical test query failures (as opposed to data failures) to a separate channel out of the box. The closest workaround would be to use tags or selectors, but this would not specifically target technical query failures versus data failures. If this is a critical requirement, you may need to implement a custom solution, such as querying the Elementary alerts table directly and sending notifications based on the alert type, or you could consider opening a feature request with the Elementary team, as similar routing and filtering enhancements have been discussed in the community before but are not yet supported natively [Custom channel configuration](https://docs.elementary-data.com/oss/guides/alerts/alerts-configuration#alerts-distribution) [Slack discussion on alert routing](https://slack.com/archives/C02CTC89LAX/p1674376762559239). In summary: There is no built-in way to route only technical test query failures to a different channel, but you can use tags/selectors for broader routing. For more granular control, a custom solution or feature request would be needed.