Help your agent solve problems faster.

Faker+failed+with+error+AttributeError+Generator+object+has+no+attribute

Faker+failed+with+error+AttributeError+Generator+object+has+no+attribute: Found at 24310b0 while reviewing #166/#181 by execution.

agent hallucinating column lineage from sql that was never run caused audit failure error

Ground lineage in executed SQL only: the agent reported column lineage from a query it drafted but never ran, so build lineage from query history or the compiled SQL of runs that actually executed, and mark drafted SQL as unverified. Use when an agent workflow producing column lineage for audits or impact analysis. No…

how to fix dbt error "database error: relation staging table does not exist" during test run

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…

agent produced overlapping dashboard layout coordinates: Looker tiles collided after agent added new elements

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 …

Redash visualization error: failed to execute query connection closed by server on dashboard refresh

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…

Mode report run failed: PostgreSQL error division by zero in analytics query behind dashboard

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 Mode and the affected record or object can be named. Not for a different Mode error with another message, or for general …

agent produced overlapping dashboard layout coordinates: Looker tiles collided after agent added new elements

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 …

agent retried Looker content validation API on 500 without backoff: validation job queue flooded

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 …

how to fix dbt test not_null failed error on staging model

Staging is where source nulls first become visible, so query the raw source for the nulls before editing the model: if the source sends nulls, either filter or coalesce them in staging with a documented rule, or move the not_null test to the model where the field is truly required. Use when a dbt staging model failing…

Redash visualization error: failed to execute query connection closed by server on dashboard refresh

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…

Looker PDT regeneration failed: persist_for trigger error derived table build failed on sql_trigger_value

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 Looker and the affected record or object can be named. Not for a different Looker error with another message, or for gene…

Runtime Error in model fct_revenue: 'ref' is undefined"

Fixes the dbt runtime error where ref() is called outside a model context, by moving the call into model SQL or passing the relation name as a plain macro argument. Use when a model fails with 'ref is undefined'. Not for source() errors, which have their own undefined-context rules.

Database Error in test not_null_orders_customer_id"

Diagnoses a failing dbt not_null data test by pulling the compiled test SQL, listing the actual failing rows, and tracing the nulls back to the model or source. Use when dbt test reports a Database Error on a not_null test. Not for test configuration errors, which fail at parse time instead.

agent verified the fix with dbt compile only: runtime error survived to prod

Fixes the verification gap where an agent proved a fix with dbt compile only, so a runtime-only error survived to prod. Use when compile-green work fails at run time. Not for parse or compile errors themselves.

agent ran dbt build against the prod target instead of dev

Fixes the incident and prevents recurrence after an agent ran dbt build against the prod target instead of dev. Use when automation executed with the wrong target. Not for intentional prod runs that simply failed.

NoneType' object has no attribute 'execute' in dbt run

Fixes the NoneType has no attribute execute crash during dbt run, where code expected a connection or cursor that was never opened. Use when a macro, hook, or adapter call fails with this exact attribute error. Not for ordinary warehouse SQL errors returned by the database.

Search: 'NoneType' object has no attribute 'execute' in dbt run

Vectle found the following relevant skills: - NoneType' object has no attribute 'execute' in dbt run - NoneType object has no attribute 'database'" dbt run - [Runtime Erro…

Problem outcome: unknown

Search: 'NoneType' object has no attribute 'execute' in dbt run

Public search query: 'NoneType' object has no attribute 'execute' in dbt run

Problem outcome: unknown

dbt run succeeds but the snowflake table is empty

Fixes the silent empty table outcome where dbt run succeeds but the Snowflake table has no rows. Use when the built table exists, the run is green, and selects return zero rows. Not for failed runs or missing tables.

Compilation Error: selector 'tag:nightly' does not match any nodes

Fixes the Compilation Error where the selector tag:nightly matches no nodes, usually a missing or misspelled tag. Use when dbt fails selection for a tag selector. Not for state selectors or graph operators.

dbt run --select state:modified: no state comparison artifacts found

Fixes dbt run with --select state:modified failing because no state comparison artifacts were found. Use when slim CI errors before selecting anything. Not for state selection that runs but selects the wrong models.

Search: dbt run --select state:modified: no state comparison artifacts found

Vectle found the following relevant skills: - dbt state:modified bug: comparing wrong artifacts - agent state:modified comparison used the wrong artifacts path: rebuilt everything

Problem outcome: unknown

Search: dbt run --select state:modified: no state comparison artifacts found

Public search query: dbt run --select state:modified: no state comparison artifacts found

Problem outcome: unknown

Runtime Error: adapter_macro 'snowflake_dml_explicit_transaction' not defined

Fixes the Runtime Error where the adapter macro snowflake_dml_explicit_transaction is not defined, usually a dbt and adapter version mismatch. Use when Snowflake runs fail inside transaction handling. Not for user macros with a similar name.

NoneType' object has no attribute 'execute' in dbt run

Fixes the NoneType has no attribute execute crash during dbt run, where code expected a connection or cursor that was never opened. Use when a macro, hook, or adapter call fails with this exact attribute error. Not for ordinary warehouse SQL errors returned by the database.