soda scan failed: failed checks found error on freshness check

Not specified by the original author.

TL;DR

Separate a real freshness breach from a broken check: confirm the table's latest event or load timestamp directly in the warehouse, then compare it with the freshness expression in the SodaCL file. If the data is stale, fix the loader; if the data is fresh, the check is reading the wrong column, timezone, or table.

soda scan failed: failed checks found error on freshness check

Use this when

• The check or run fails with this symptom: the Soda scan exits non-zero and the freshness check is listed as failed.
• You are working on a Soda scan whose freshness check reports failed checks found 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 scan that cannot connect at all, which is a datasource configuration problem instead.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Run the scan with verbose output and record the measured freshness value Soda computed, not just the pass or fail label. Verify: you have the measured age Soda used for the decision
2. Query the warehouse directly for the maximum of the freshness column on the same table Soda scanned. Verify: the warehouse maximum timestamp is known for comparison
3. Compare the two values and inspect the SodaCL freshness expression for the column name, the warehouse timezone handling, and any filter that excludes recent rows. Verify: any mismatch between the Soda expression and the warehouse value is explained
4. Fix the stale side: restart or backfill the loader if the data is old, or correct the column, timezone, or threshold in the SodaCL file if the data is current. Verify: the corrected check measures the real table state
5. Rerun the soda scan and confirm the exit code and the freshness check both pass. Verify: the scan exits zero with the freshness check green

Variant phrasings

soda scan failed checks found freshness

The exit-code phrasing from CI logs.

soda freshness check failed but data is fresh

The false-alarm phrasing, pointing at column or timezone mistakes in the SodaCL file.

soda scan freshness threshold configuration

The configuration phrasing for tuning the threshold and column.

Compatibility: Soda Core and SodaCL with Snowflake, BigQuery, Postgres, and Spark connections

Why it happens

Soda evaluates the freshness expression against the warehouse at scan time and fails the scan when the measured age exceeds the threshold. The failure therefore has two very different causes: the pipeline genuinely stopped loading, or the check points at a column or table that no longer reflects loading, and the summary line does not distinguish them.

Edge cases / pitfalls

• Freshness on a load timestamp measures the loader, not the event time. Pick the column that matches the SLA being promised.
• Weekend and holiday gaps trip fixed thresholds. Use a threshold that reflects the real load cadence.

Provenance

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

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

Thread query: soda scan failed: failed checks found error on freshness check

TL;DR: Separate a real freshness breach from a broken check: confirm the table's latest event or load timestamp directly in the warehouse, then compare it with the freshness expression in the SodaCL file. If the data is stale, fix the loader; if the data is fresh, the check is reading the wrong column, timezone, or table.

Not specified by the original author.

TL;DR

Separate a real freshness breach from a broken check: confirm the table's latest event or load timestamp directly in the warehouse, then compare it with the freshness expression in the SodaCL file. If the data is stale, fix the loader; if the data is fresh, the check is reading the wrong column, timezone, or table.

soda scan failed: failed checks found error on freshness check

Use this when

• The check or run fails with this symptom: the Soda scan exits non-zero and the freshness check is listed as failed.
• You are working on a Soda scan whose freshness check reports failed checks found 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 scan that cannot connect at all, which is a datasource configuration problem instead.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Run the scan with verbose output and record the measured freshness value Soda computed, not just the pass or fail label. Verify: you have the measured age Soda used for the decision
2. Query the warehouse directly for the maximum of the freshness column on the same table Soda scanned. Verify: the warehouse maximum timestamp is known for comparison
3. Compare the two values and inspect the SodaCL freshness expression for the column name, the warehouse timezone handling, and any filter that excludes recent rows. Verify: any mismatch between the Soda expression and the warehouse value is explained
4. Fix the stale side: restart or backfill the loader if the data is old, or correct the column, timezone, or threshold in the SodaCL file if the data is current. Verify: the corrected check measures the real table state
5. Rerun the soda scan and confirm the exit code and the freshness check both pass. Verify: the scan exits zero with the freshness check green

Variant phrasings

soda scan failed checks found freshness

The exit-code phrasing from CI logs.

soda freshness check failed but data is fresh

The false-alarm phrasing, pointing at column or timezone mistakes in the SodaCL file.

soda scan freshness threshold configuration

The configuration phrasing for tuning the threshold and column.

Compatibility: Soda Core and SodaCL with Snowflake, BigQuery, Postgres, and Spark connections

Why it happens

Soda evaluates the freshness expression against the warehouse at scan time and fails the scan when the measured age exceeds the threshold. The failure therefore has two very different causes: the pipeline genuinely stopped loading, or the check points at a column or table that no longer reflects loading, and the summary line does not distinguish them.

Edge cases / pitfalls

• Freshness on a load timestamp measures the loader, not the event time. Pick the column that matches the SLA being promised.
• Weekend and holiday gaps trip fixed thresholds. Use a threshold that reflects the real load cadence.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_2eh3M1Ep3pN-R0SJyUPHxQ

Resolved from the public thread: https://vectle.com/posts/pst_2eh3M1Ep3pN-R0SJyUPHxQ

Thread query: soda scan failed: failed checks found error on freshness check

TL;DR: Separate a real freshness breach from a broken check: confirm the table's latest event or load timestamp directly in the warehouse, then compare it with the freshness expression in the SodaCL file. If the data is stale, fix the loader; if the data is fresh, the check is reading the wrong column, timezone, or table.

Not specified by the original author.

TL;DR

Fix the connection in layers: validate the datasource block in the Soda configuration file, test the same credentials and host with the warehouse's own client, and only then debug Soda-specific options. Soda reports one connect error for bad hosts, wrong ports, expired credentials, and missing drivers, so isolate each layer separately.

soda core error: soda scan failed to connect warehouse error

Use this when

• The check or run fails with this symptom: soda scan fails during connection before any check runs.
• You are working on a Soda setup that cannot connect to its warehouse 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 scan that connects but fails individual checks, which is a data or SodaCL problem instead.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Run soda scan with the verbose flag and capture the underlying driver error beneath the Soda connect message. Verify: the driver-level error text is captured
2. Check the datasource configuration for host, port, database, schema, and the environment variable names supplying the username and credential values. Verify: every connection field is confirmed against the warehouse settings
3. Connect with the warehouse's native client using the identical host, user, and credential to prove the path outside Soda. Verify: the native client either connects or reproduces the failure outside Soda
4. Confirm the required Python driver package for that warehouse is installed in the same environment that runs Soda. Verify: the driver import succeeds in the Soda environment
5. Rerun the soda scan with a single trivial check to prove the connection before restoring the full check set. Verify: the trivial scan connects and completes

Variant phrasings

soda scan failed to connect warehouse

The verbatim connect phrasing.

soda core datasource configuration connection error

The configuration phrasing for the datasource block and environment variables.

soda scan driver not installed warehouse

The driver phrasing for missing Python driver packages.

Compatibility: Soda Core 3 and 4 with Snowflake, BigQuery, Redshift, Postgres, and Databricks datasources

Why it happens

Soda delegates to warehouse drivers, and any break in the chain of configuration values, environment variables, network path, credentials, or driver installation surfaces as the same connect failure. The scan never reaches the checks, so no check tuning can fix it.

Edge cases / pitfalls

• Credentials rotated in the warehouse must also be rotated in the environment Soda reads. Check both stores.
• A VPN or allowlist change can break only the Soda runner. Test from the same host that runs the scan.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_10RJX-l0e0dQUH5D-8j6nA

Resolved from the public thread: https://vectle.com/posts/pst_10RJX-l0e0dQUH5D-8j6nA

Thread query: soda core error: soda scan failed to connect warehouse error

TL;DR: Fix the connection in layers: validate the datasource block in the Soda configuration file, test the same credentials and host with the warehouse's own client, and only then debug Soda-specific options. Soda reports one connect error for bad hosts, wrong ports, expired credentials, and missing drivers, so isolate each layer separately.