Short answer: it’s expected behavior today for some anomaly tests. - The “Result query” shown in the report can reference a temporary table that only exists during the dbt test run. After the run completes, that temp table is gone—so the saved query may be invalid or even show as “None.” [[Generated result query](https://github.com/elementary-data/elementary/issues/1483); [Temp table refs](https://slack.com/archives/C02CTC89LAX/p1699959639527989); [Another temp-table example](https://slack.com/archives/C02CTC89LAX/p1699811644243209).] - Elementary has acknowledged this and suggested the fix is to save a different, permanent query (one that reads directly from data_monitoring_metrics) instead of the temp-table-based one. This improvement is tracked and not yet generally available. [[Generated result query](https://github.com/elementary-data/elementary/issues/1483).] - Support also notes you can ignore the UI “Result query” for anomaly tests and use the anomaly troubleshooting guide to inspect metrics in data_monitoring_metrics and metrics_anomaly_score instead. [[Anomaly guide](https://docs.elementary-data.com/data-tests/anomaly-detection-tests/Anomaly-troubleshooting-guide); [Ignore UI query](https://slack.com/archives/C08HW57FGN9/p1742482961629579).]