A freshness check has two failure modes that look identical in most tools.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/warehouse-freshness-auditor.mjs \
--policy examples/clean/freshness.policy.json \
--snapshot examples/clean/snapshot.json \
--now 2026-09-18T09:00:00ZRead the result
A late table whose cause could not be settled exits 2 rather than 1: the cause is part of what this tool exists to report, and cause-undetermined says so. Governing the upstream tables in the policy is what turns such a run into a clean exit 1 with the chain named.
Where this check stops
Every bound is enforced before the work it bounds, not after. The snapshot's size is taken from stat before the file is opened.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.