Elementary Community

I was able to get it to work by dropping both `alerts_source_freshness` and `alerts_dbt_source_freshness` table/view, but the error has returned again today after more alerts have been generated (we run all our models just once per day).

The only change that I could see was <https://github.com/elementary-data/elementary/commit/1ac5f99a4ebe2d22ea2ce668d3973e40c69e07c7|here>

We're using the databricks connector and looking at the logs we have
```  merge into `production`.`elementary`.`alerts_source_freshness` as DBT_INTERNAL_DEST
      using `alerts_source_freshness__dbt_tmp` as DBT_INTERNAL_SOURCE ...```
and `alerts_source_freshness__dbt_tmp` is created with
```create temporary view `alerts_source_freshness__dbt_tmp` as
    select 
      *,
      false as alert_sent,  
      'pending' as suppression_status,
      cast(NULL as string) as sent_at
    from `production`.`elementary`.`alerts_dbt_source_freshness````
there seems to be a mismatch - the two datasets have different schemas
Is this expected?

I dropped `alerts_source_freshness` only this time and everything seems to work repeatedly now. :white_check_mark: