freshness check failed error: table not updated in 24 hours stale data failure

TL;DR

Prove whether the table is stale or the clock is wrong: check the table's latest load and event timestamps directly, compare them with the freshness window and the timezone the check uses, and inspect the loader's last successful run. A table untouched for 24 hours with a healthy loader usually means the check reads the wrong timestamp column.

freshness check failed error: table not updated in 24 hours stale data failure

Use this when

• The check or run fails with this symptom: the freshness check reports the table as not updated within 24 hours.
• You are working on a freshness check failing on a table that should update daily and the failure repeats on the same data or configuration.
• You need the failing rows, rule, or stage isolated before changing thresholds or code.

Not for this skill when

• A volume anomaly with fresh timestamps, which points at counts rather than timing instead.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Query the maximum event timestamp and the maximum load timestamp on the table and record both. Verify: both timestamps are known and compared
2. Review the loader or orchestration history for the last successful run and any skipped or failed runs in the window. Verify: the loader's recent run history is established
3. Inspect the freshness check configuration for the timestamp column, the threshold, and the timezone it assumes. Verify: the check's column, threshold, and timezone are explicit
4. Fix the failing side: rerun or backfill the loader if data is missing, or correct the check's column or timezone if data is current. Verify: the correction matches the confirmed cause
5. Rerun the freshness check after the next load cycle and confirm it passes on fresh data. Verify: the check passes on the following cycle

Variant phrasings

freshness check failed table not updated 24 hours

The verbatim stale phrasing.

freshness check failed but table updated timezone

The false-alarm phrasing for timezone and column mistakes.

dbt source freshness error stale data

The dbt source-freshness phrasing.

Compatibility: Soda, dbt source freshness, Monte Carlo style monitors, and custom freshness checks

Why it happens

Freshness checks compare a stored timestamp with a window, so loader outages, timezone mismatches between the check and the warehouse, and checks pointed at event time while loads batch overnight all produce the same stale verdict on very different underlying states.

Edge cases / pitfalls

• Separate event freshness from load freshness in the check names. Teams debug the wrong one constantly.
• Holiday and weekend cadences need calendar-aware thresholds or the check cries wolf weekly.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_WfM1cvOqIk3mHWTC2vxFhg