I am running into an issue that I'm not sure about:

17:03:30    Database Error in model alerts_source_freshness (models/alerts/alerts_source_freshness.sql)
  Value has type TIMESTAMP which cannot be inserted into column detected_at, which has type STRING at [30:338]
  compiled Code at target/run/elementary_cli/models/alerts/alerts_source_freshness.sql
17:03:30
17:03:30    Database Error in model alerts_models (models/alerts/alerts_models.sql)
  Value has type TIMESTAMP which cannot be inserted into column detected_at, which has type STRING at [30:175]
  compiled Code at target/run/elementary_cli/models/alerts/alerts_models.sql

Should I be changing the datatype in BigQuery to STRING for detected_at column? I'm hesitant to manually change the datatypes since presumably Elementary created these tables itself. It says it's command is

dbt run -m elementary_cli.alerts

(with some paths as well) This is Elementary 0.12.2 running on python3.12 against BigQuery.

Hi @Renee Cooper, thanks for surfacing! Looks related to a recent change, I'll have a look into this

@Itamar Hartstein Hey! Just wondwring if is there any update on this issue as I'm running into a similar one as well.

I'm assuming this is why our dashboard shows all green/passing even though we have a few failing tests -- it's not recording them in the alerts table?

Hi @Renee Cooper, sorry for the delay, yes we issued a fix - please upgrade both the dbt package and CLI to version 0.13.0 and run the elementary models (

dbt run -s elementary

) and it should fix the alerts issue. However doesn't sound related to the dashboard - is it possible that the failing tests are not the latest result?