Based on the information provided and the knowledge sources, the "No data" status for automated cloud freshness & volume anomaly monitors typically means that Elementary Cloud could not find any recent updates or query activity for the monitored tables in your data warehouse's metadata or query history. This is explicitly indicated by the message: "Table not found in query history for the past 23 days. Confirm that the queries were actually executed." Here are the most likely reasons for this issue: 1. No Recent Table Updates: Automated monitors rely on warehouse metadata (such as information schema or query history) to detect when tables are updated. If there have been no DML operations (INSERT, UPDATE, etc.) on the tables within the monitored period, the monitor will not have any data to analyze, resulting in a "No data" status. This can happen if the tables are static, not being loaded, or if the data pipeline is not running as expected. 2. Table Not Found in Query History: If the table does not appear in the warehouse's query history, Elementary cannot determine when it was last updated. This could be due to: - The table genuinely not being updated. - The table being dropped and recreated (which may break the metadata lineage). - The monitoring user not having sufficient permissions to access the query history or information schema for those tables. 3. Initial Backfill Not Complete: When you first set up Elementary Cloud, it performs a backfill to collect historical metadata. If this process did not complete successfully, or if there is not enough historical data (at least 21 days by default), the monitors may not be operational yet and will show "No data" until enough history is collected and updates are detected [Automated Freshness & Volume Monitors](https://docs.elementary-data.com/features/anomaly-detection/automated-monitors). What you should check: - Ensure that your data pipelines are running and that the tables are being updated as expected. - Verify that the monitoring user has access to the necessary metadata and query history in your data warehouse. - Confirm that the tables have not been dropped/recreated in a way that would break their metadata lineage. - Wait for the initial backfill to complete if you have just set up Elementary Cloud. If all of the above are in order and you still see "No data," it may be necessary to reach out to Elementary support for further troubleshooting, as there could be an environment-specific issue [Anomaly Detection Monitors](https://docs.elementary-data.com/features/anomaly-detection/monitors-overview). Summary: The "No data" status means Elementary Cloud cannot find recent updates for your tables in the warehouse metadata. This is usually due to a lack of recent table activity, missing permissions, or incomplete metadata backfill. Double-check your data pipeline activity and warehouse access to resolve the issue.