agent failed to map soda checks to dbt tests after yaml key rename error failed

TL;DR

Rebuild the mapping from the current files: a Soda YAML key rename changed the check identifiers the agent mapped to dbt tests, so regenerate the mapping by parsing both current files instead of patching the stale map by hand. The mapping broke because it was keyed on names that changed. Any mapping stored outside the files it maps will rot the same way on the next rename.

agent failed to map soda checks to dbt tests after yaml key rename error failed

Use this when

• The check or run fails with this symptom: an agent fails to map Soda checks to dbt tests after a YAML key rename.
• You are working on an agent workflow that keeps Soda checks and dbt tests in sync for the same 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 rename that also changed the check logic, where the mapping is the least of the work and the checks need review.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Diff the Soda checks file against its previous version. Verify: the renamed keys are listed
2. Parse the current Soda checks and the current dbt schema tests into a common list of table, column, and check type. Verify: both sides are described in the same terms
3. Regenerate the mapping from the parsed lists and report any check with no counterpart. Verify: every current check is mapped or explicitly unmatched
4. Run one mapped pair end to end. Verify: the Soda result and the dbt result refer to the same table and rule
5. Store the mapping generation as a step in the workflow, not as a saved file. Verify: the next rename regenerates instead of breaking

Variant phrasings

agent failed map soda checks dbt tests yaml rename

The shorter phrasing focused on the named failure.

soda dbt test mapping broken key rename

The symptom phrasing a searcher tries next.

soda checks dbt tests sync fix

The variant naming the failing stage or tool directly.

Compatibility: Soda Core checks YAML and dbt schema tests, agent sync workflows

Why it happens

Teams duplicate the same rule in Soda and dbt and map them by name. A rename in one file, often a cleanup of check keys, invalidates every stored reference at once, and the agent fails because its map describes files that no longer exist in that form.

Edge cases / pitfalls

• Name based mapping is fragile even without renames; include table and column in the match key so a rename is a diff, not a break.
• Unmatched checks after regeneration are findings, not errors; report them rather than forcing a match.

Provenance

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