https://linen.dev logo
Join Slack
Powered by
<@U088WCP3B4P> Hi! I have config block that looks ...
# ask-elementary-ai
e
@kapa.ai Hi! I have config block that looks like this:
Copy code
{{
    config(
            meta={
            "owner": "@name.surname"
            },
            materialized='incremental',
            unique_key=['search_id', 'item_id'],
            dist='item_id',
            sort='search_created_at',
            tags=["flow:search_funnel", "schedule:daily"] )
}}
when I run 
edr monitor
I get a Slack message in the correct channel warning me of the failed test, but NO tagging of the owner happens. Why?
k
A message from kapa.ai
Based on the knowledge sources, there are a few common reasons why the owner is not being tagged in Slack alerts, even when the config block appears correct: 1. Owner Format: The owner should be specified as the Slack handle with an @ and the email prefix, e.g., 
@name.surname
. This matches your config, so the format seems correct, assuming 
@name.surname
is the actual Slack handle and not just a placeholder. Double-check that the handle matches exactly what appears in Slack (no extra spaces, correct case, etc.)—mistakes here are a frequent cause of this issue. For example, if your Slack email is 
<mailto:name.surname@company.com|name.surname@company.com>
, then 
@name.surname
is correct. If you use the full email or Slack user ID, it will not work for tagging in alerts. Also, ensure there are no hidden characters or spaces in the config value, as these can prevent proper tagging [Owners and subscribers](https://docs.elementary-data.com/features/alerts-and-incidents/owners-and-subscribers), [Slack forum: @ mention issues](https://slack.com/archives/C02CTC89LAX/p1710042179246249), [Slack forum: @ mention string not tagging](https://slack.com/archives/C02CTC89LAX/p1697221207875479). 2. Elementary Version: There have been bugs in past versions of Elementary where owner tagging did not work as expected, especially after certain refactors. Make sure you are using a version where this is fixed (e.g., 0.6.10 or later for some known issues) [Slack forum: owner not tagged bug](https://slack.com/archives/C02CTC89LAX/p1675155349351339). 3. dbt Run Required: After changing owner metadata, you must run a dbt command (like 
dbt run --select elementary
or 
dbt build
) to update the metadata that Elementary uses. If you only run 
edr monitor
without updating the dbt artifacts, the new owner info may not be picked up [Slack forum: dbt run required](https://slack.com/archives/C02CTC89LAX/p1696423169407779). 4. Model vs. Test Level: If this config is on a model, it should work. If you are trying to tag owners on a test (especially a singular/custom test), there have been limitations in the past where only model-level owners are supported for tagging in alerts. Subscribers can be set at the test level, but owner tagging may not work for custom tests unless this has been addressed in your version [Slack forum: test-level owner not supported](https://slack.com/archives/C02CTC89LAX/p1667915416294299), [Slack forum: custom test owner limitations](https://slack.com/archives/C02CTC89LAX/p1675867987431539). 5. Pipeline Differences: If it works locally but not in CI/CD (e.g., GitLab), ensure all versions (dbt, Elementary, Python, adapters) match exactly, and that the dbt artifacts are up to date in the pipeline environment [Slack forum: owner missing in GitLab](https://slack.com/archives/C02CTC89LAX/p1709813517633099). Summary of what to check: - Confirm the owner value matches the Slack handle format exactly. - Ensure you are on a recent Elementary version. - Run 
dbt run
or 
dbt build
after changing metadata. - If this is a test-level config, be aware of possible limitations. - Check for environment/version mismatches if running in CI/CD. If all of the above are correct and it still does not work, it may be a bug or a limitation in your Elementary version. In that case, consider upgrading or opening an issue with the Elementary team. Let me know if you need help troubleshooting any of these steps!
32 Views
Open in Slack
PreviousNext
Powered by