Hi folks! Currently working on volume anomalies in a data sources within my dbt project. Many of the source tables in my project are overwritten with each delivery, meaning the timestamp column only contains information relevant to the delivery day (this morning). The dbt job runs after all pipelines have finished ingesting the sources. However, the challenge arises with

elementary.volume_anomalies

, where the last period considered is yesterday. Therefore, under the logic explained above, it never manages to capture the volume of data ingested for tables that are in overwrite mode. Does anyone have any suggestions on how I can address these cases? Thanks in advance!

Hey @Jorge Simonovich, You should use the test without a timestamp column. This way each test execution will count the total volume, and after there are enough data points (14 days if daily execution) the test will start comparing the last row count to the previous data points.

Thanks a lot!