Skip to main content

Hello! One of the engineers on my team noticed that when trying to configure notifications for when Anomalies are detected on a monitoring project that it only works if the Data Observability for the source is also configured for Anomaly Detection and to send emails. Is this behavior anyone else has experienced in V 16.2? Is this intentional? It seems odd that these would be linked, I would think that users would want to be able to configure Anomaly Detection independently either at the source or the project level, and that the audiences for those anomalies might be different.

We’re currently working through a bug where this is working this way in our dev instance and not working at all in our production environment. To clarify, this is not about the general Monitoring Project Run Completed email, which includes info on anomalies, data quality, etc., this is just about the “Anomalies Detected” notification on monitoring projects. This has occurred in multiple instances in Dev and has not worked at all in multiple instances in Prod, both of which are on the same version of the tool (16.2).

Yes, we're experiencing the same issue. In the latest 16.2 version, I had to configure Data Observability at the Data Source level to start receiving anomaly detection emails, which feels a bit unusual. However, it's only working for us in the DEV region. When I try to configure Data Observability at the Data Source level and save it in PROD, I encounter a random API error.


Yes, we're experiencing the same issue. In the latest 16.2 version, I had to configure Data Observability at the Data Source level to start receiving anomaly detection emails, which feels a bit unusual. However, it's only working for us in the DEV region. When I try to configure Data Observability at the Data Source level and save it in PROD, I encounter a random API error.

Hi there, we are also experiencing the same issue with Data Observability. When we try to configure schema detection or teams notifications of the PROD instance, it throws us an unknown error.


Yes, we're experiencing the same issue. In the latest 16.2 version, I had to configure Data Observability at the Data Source level to start receiving anomaly detection emails, which feels a bit unusual. However, it's only working for us in the DEV region. When I try to configure Data Observability at the Data Source level and save it in PROD, I encounter a random API error.

Hi there, we are also experiencing the same issue with Data Observability. When we try to configure schema detection or teams notifications of the PROD instance, it throws us an unknown error.

Hey, apejko! Teams notifications do not work currently, I believe. They previously worked with webhooks being sent to Teams, but support for that began to end beginning in August of 2024 and I guess fully ending in December of 2025, with Microsoft changes. I think it is on the Ataccama roadmap to implement new functionality using workflows/PowerAutomate integration for Teams to replace the old webhooks design.