Hunt the child rows, not the test: a dbt relationships test fails when fact rows carry a key with no parent, so list the unmatched keys, then decide per key whether the parent is missing, the key is mistyped, or the fact arrived early. Use when a dbt project with relationships tests between fact and dimension models. …
Vectle found the following relevant skills: - dbt test failed: relationships test on orders" - dbt test error: accepted_values test failed with unexpected value error - [d…
Fixes this failure in the Clay waterfall step - open the failing waterfall step, check what input column it received - it needs a domain or an email address, not a company name alone - fix the column mapping, and set the step to continue to the next provider when this one returns empty. Prove it on one record, then re…
Fix the reference, not the test: a test that depends on a missing model ref means the generic or singular test is attached to a model name that does not exist in the project, usually after a rename or a moved file. Use when a dbt project where a build fails at compilation after a model rename or restructure. Not for a…
Create the staging relation before the test run, in the right schema: the test queried a staging table that the run never built, usually because the test ran standalone, the model was deselected, or the schema macro resolves differently under the test target. Use when a dbt project running tests against a target where…
Vectle found the following relevant skills: - dbt test failed: unique test flagged duplicates from null values - dbt test failed: unique_combination_of_columns failed with duplicate keys error
Vectle found the following relevant skills: - dbt test failed: unique_combination_of_columns failed with duplicate keys error - dbt test failed: unique_combination_of_columns failed with duplicate keys error
Vectle found the following relevant skills: - dbt test failed: unique_combination_of_columns failed with duplicate keys error - dbt test failed: unique_combination_of_columns failed with duplicate keys error
Compare the live object state against the config that produced it, fix the first differing value at its source, and re run the single affected item. Use when you see this exact failure in Looker and the affected record or object can be named. Not for a different Looker error with another message, or for general setup …
Find the last successful refresh or calculation timestamp, fix what stopped that job, force one refresh, and compare the served value against a direct query of the source. Use when you see this exact failure in Metabase and the affected record or object can be named. Not for a different Metabase error with another mes…
A singular test fails by design when its SQL returns rows, so read the returned rows as the bug report: run the test SQL from the tests folder directly, inspect the first rows, and fix the model logic or the data those rows expose. Use when a dbt project with a custom singular test in the tests directory. Not for a ge…
Find the duplicated key combination before touching the test: run the test query grouped by the key columns, inspect the duplicate groups, and fix the join or fan-out that creates them, or correct the key if the declared combination is not actually unique in the business data. Use when a dbt model whose declared uniqu…
Vectle found the following relevant skills: - dbt test failed: unique_combination_of_columns failed with duplicate keys error - Unique test failed: duplicate values in primary key" dbt
Walk the chain in order and test each hand off with one known record, fix the first hand off where the record disappears, and add a log line at that hand off. Use when you see this exact failure in Redash and the affected record or object can be named. Not for a different Redash error with another message, or for gene…
Vectle found the following relevant skills: - dbt singular test failure: assertion failed error rows returned - dbt test failed: relationships test on orders" - [dbt test …
Summarize dbt results from the run_results artefact in aggregate instead of pasting it into the prompt: count statuses per model and test, keep only failures with their messages, and cap the failure detail list with a pointer to the artefact file. Use when an agent reporting dbt test outcomes after a run. Not for one …
Vectle found the following relevant skills: - context overflow when agent tried to compare all annotator pairs failed error - context overflow when agent tried to load all anomaly alerts error failed memory