What causes SnapshotTimestampColumnNotFound?

The source table's updated_at column was renamed (e.g., to modified_at or last_updated) without updating the snapshot's updated_at config. The snapshot was configured to use a column from a joined source, but the final source model does not expose that column by that name. The updated_at column was dropped from the source during a schema migration and the snapshot config was not updated to match

How do I fix SnapshotTimestampColumnNotFound?

Step 1: Query the source table to confirm the exact column name: SELECT column_name FROM information_schema.columns WHERE table_name = ' '.. Step 2: Update the snapshot's updated_at config to the correct column name.. Step 3: If no suitable timestamp column exists in the source, consider switching to the check strategy with explicit check_cols instead of the timestamp strategy.. Step 4: Run dbt snapshot after fixing the config to verify the snapshot executes cleanly.

High severitycompilation

Power BI Refresh Error:
SnapshotTimestampColumnNotFound

What does this error mean?

A dbt snapshot using the timestamp strategy failed because the column specified in updated_at does not exist in the source relation, causing the snapshot query to raise a column-not-found compilation or SQL error.

Common causes

1The source table's updated_at column was renamed (e.g., to modified_at or last_updated) without updating the snapshot's updated_at config
2The snapshot was configured to use a column from a joined source, but the final source model does not expose that column by that name
3The updated_at column was dropped from the source during a schema migration and the snapshot config was not updated to match

How to fix it

1Step 1: Query the source table to confirm the exact column name: SELECT column_name FROM information_schema.columns WHERE table_name = '<source>'.
2Step 2: Update the snapshot's updated_at config to the correct column name.
3Step 3: If no suitable timestamp column exists in the source, consider switching to the check strategy with explicit check_cols instead of the timestamp strategy.
4Step 4: Run dbt snapshot after fixing the config to verify the snapshot executes cleanly.

Frequently asked questions

Can dbt automatically discover the timestamp column?

No. dbt requires the updated_at column to be explicitly named in the snapshot configuration. There is no auto-discovery of timestamp columns.

What if my source has no reliable updated_at column?

Switch to the check strategy with a curated list of check_cols that represent meaningful business attributes. This requires a full-table scan on each run but works without a timestamp.