Based on the available knowledge sources, there is no explicit documentation or announcement about a recent change that would have removed the alert type indicators (such as 🔺 dbt test alert, ⚠️ dbt source freshness alert, etc.) from the beginning of Slack alert messages and replaced them with a generic "Failure" prefix. However, there are user questions in the community about customizing or changing the default title or appearance of Slack alerts, with responses indicating that customization of the alert title is not currently supported, but feature requests are welcome. For example, one thread confirms that it's not possible to change the default title of Slack alerts at this time, and another confirms that the string "dbt test alert" is not currently customizable, but users are encouraged to submit feature requests if they have specific needs or feedback. There is no mention of a change that would have made all alerts start with "Failure" by default, nor is there documentation of such a change in the release notes or support threads provided in your sources [Slack thread: default title of Slack alerts](https://elementary-community.slack.com/archives/C08HW57FGN9/p1744891375937179?thread_ts=1744891375.937179&cid=C08HW57FGN9), [Slack thread: adjust "dbt test alert" string](https://elementary-community.slack.com/archives/C02CTC89LAX/p1691608483808449?thread_ts=1691608483.808449&cid=C02CTC89LAX). If you are now seeing all alerts start with "Failure" and missing the previous alert type indicators, this may be due to a recent update or configuration change not covered in the current documentation or community threads. If this change is causing issues for your workflow, it is recommended to reach out to the Elementary support team or submit a feature request describing your use case and the impact of this change. I'm sorry, but the knowledge sources do not contain enough information to confirm when or why this change to alert appearance may have occurred.

You can configure Elementary to use a specific schema for its test tables by setting the schema in your

dbt_project.yml

file. For example:

yaml models:   elementary:     +schema: elementary

This will ensure that all Elementary tables (metadata and test tables) are created in the specified schema. If you want to use a separate schema specifically for Elementary test tables, you can set the following variable:

yaml vars:   tests_schema_name: 'elementary_tests'

This approach is supported and recommended to keep Elementary artifacts organized and separate from your other models. However, if you are considering using the same schema for multiple dbt projects, be aware that this is not recommended. Elementary does not support multiple dbt projects writing to the same schema, as this can lead to conflicts and data being overwritten between projects. Each dbt project should have its own dedicated Elementary schema to avoid such issues [Can I change the Elementary schema?](https://docs.elementary-data.com/oss/general/faq), [Slack thread: single schema for multiple projects](https://elementary-community.slack.com/archives/C02CTC89LAX/p1693465315902869?thread_ts=1693465315.902869&cid=C02CTC89LAX), [Slack thread: same schema for multiple projects](https://elementary-community.slack.com/archives/C02CTC89LAX/p1729496312147559?thread_ts=1729496312.147559&cid=C02CTC89LAX). In summary: - Yes, you can use the same schema for all Elementary test tables within a single dbt project. - No, you should not use the same schema for Elementary across multiple dbt projects, as this will cause conflicts and data loss.