dst-check-freshness

Data freshness checks compare your local table's last update timestamp against a maximum age threshold to determine whether a refresh is required. Use the CLI metadata check with --table-id and --max-age-days to get the data age and threshold status instantly.

Freshness measures how old your local copy is by calculating the gap between the last_updated timestamp and the current fetch time. Stale data can skew analysis results, so freshness validation ensures you're working with current information before proceeding with workflows.

Yes. The freshness check outputs actionable outcomes—comparing data age against your max-age setting—to guide whether to refresh or proceed with analysis, enabling automated validation within CLI-based analysis pipelines.

Run the metadata check script with your table ID and desired maximum age in days. It returns Last Updated, Fetch Timestamp, Data Age, and Threshold status to inform your refresh decision before starting downstream analysis.

When data age surpasses your max-age-days limit, the freshness check flags it as stale and recommends refreshing from DST. This prevents analysis on outdated information and maintains data quality across your workflows.