soda scan failed error "for each table configuration not found in soda.yml"

TL;DR

Match the scan to the config layout Soda expects: a for each table block needs the table set defined or discoverable in the Soda configuration, so define the tables explicitly in soda.yml or fix the configuration reference the scan is pointed at. Soda resolves for each table against the data source configuration. When the scan runs against a configuration that does not define the tables, the expansion has nothing to iterate and the scan fails before any check runs.

soda scan failed error "for each table configuration not found in soda.yml"

Use this when

• The check or run fails with this symptom: a Soda scan fails with for each table configuration not found in soda.yml.
• You are working on a Soda Core scan using for each table checks across a set of tables 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 failing on a single named table check, where the table itself is missing from the warehouse rather than the configuration.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Open the soda.yml the scan actually loaded and look for the for each table definition. Verify: the loaded file and its table set are confirmed, not assumed
2. Check the scan command or task configuration for the configuration file path being passed. Verify: a wrong or stale config path is found or ruled out
3. Define the table set for the for each block, or list the tables explicitly in the checks file. Verify: the scan expands the block into per-table checks
4. Run the scan in verbose mode on one table set. Verify: per-table checks execute and report individually
5. Run the full scan. Verify: all tables in the set are checked with no configuration error

Variant phrasings

soda for each table configuration not found soda.yml

The shorter phrasing focused on the named failure.

soda scan failed for each table not found

The symptom phrasing a searcher tries next.

soda.yml for each table configuration fix

The variant naming the failing stage or tool directly.

Compatibility: Soda Core 3.x, soda.yml data source and checks files

Why it happens

For each table is an expansion feature that reads its table list from configuration at scan start. Pointing the scan at a minimal soda.yml, or splitting configuration across files that are not all loaded, leaves the expansion undefined even though the checks file parses fine on its own.

Edge cases / pitfalls

• Configuration split across multiple files needs every file passed to the scan; loading only the checks file is the common miss.
• Table names in the set are matched literally; a schema prefix difference makes an existing table look unconfigured.

Provenance

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

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

Thread query: soda scan failed error "for each table configuration not found in soda.yml"

TL;DR: Match the scan to the config layout Soda expects: a for each table block needs the table set defined or discoverable in the Soda configuration, so define the tables explicitly in soda.yml or fix the configuration reference the scan is pointed at. Soda resolves for each table against the data source configuration. When the scan runs against a configuration that does not define the tables, the expansion has nothing to iterate and the scan fails before any check runs.