Hi, I would like to check the freshness of some tables, but the elementary.freshness_anomalies tests do a different check than I expected, calculating the difference between adjacent data. Is there any way to configure a test that goes to check, for example, that the previous day's data has been loaded, without having to write a custom dbt test? An operation similar to dbt's freshness checks:

freshness: 
  error_after: {count: 24, period: hour}
  filter: modifiedon > DATE_SUB(CURRENT_DATE(), INTERVAL 3 DAY)
  loaded_at_field: "CAST(modifiedon AS TIMESTAMP)"

Hey @Simone CAVALLERA, why dont you just use dbt's freshness checks?

Hi @Ofek Weiss, yes. I finally found the solution by mapping the dbt freshness test to elementary. Thank you.