Compilation Error: 'config' is undefined in test definition

Not specified by the original author.

TL;DR

Generic test definitions do not get the model config function. Move the settings into the test YAML arguments or into the test SQL itself: set severity and thresholds as test arguments in schema.yml, and drop the config call from the test file. The test then parses and runs with the intended severity.

Compilation Error: 'config' is undefined in test definition

Use this when

• dbt test or dbt build fails at parse time saying config is undefined in test definition
• the failing file lives under tests/ or is a generic test defined in a macro-like test block
• the error appeared after copying model boilerplate, including a config block, into a test

Not for this skill when

• the config call is at the top of a normal model file, that is supported and the cause is elsewhere
• you need per-model materialization settings, those belong in the model or in dbt_project.yml
• the error names a different undefined name such as ref or source

Steps

1. Open the failing test file and find the config call. Note exactly which keys it sets, commonly severity, warnif, errorif, or store_failures. Verify: you have a written list of the settings that must survive the move.

2. Delete the config block from the test definition. In schema.yml, pass the same settings as arguments on the test instance, for example severity: warn and store_failures: true under the test entry for that column. Verify: schema.yml carries the settings and the test file has no config call.

3. If the test is defined once and reused with different thresholds, declare formal arguments in the test definition using the test block argument syntax and read them with kwargs instead of config. Verify: dbt parse completes with no undefined name error.

4. Run dbt test --select on one model using the test and force a failing row in dev to confirm the severity and store_failures behavior still match the old config. Verify: the test runs, reports with the expected severity, and failing rows are stored when configured.

Variant phrasings

config undefined in a singular test

Singular tests in tests/ are plain SQL with ref and source available, but config is limited there too. Set singular test severity in schema.yml is not possible, so gate the SQL or accept default severity.

worked before an upgrade

Older dbt versions were laxer about stray config calls in some test paths. Treat the stricter parse as correct and move the settings to YAML.

Compatibility: dbt-core 1.5 and later generic and singular tests; schema.yml test arguments on all adapters. Config blocks remain valid at the top of model SQL files.

Why it happens

dbt renders different Jinja contexts for different resource types. Models get config because materialization is a model concern. Test definitions get a narrower context focused on the test query and its arguments, so the name config simply is not defined there and the parser raises instead of ignoring it.

Edge cases / pitfalls

• storefailures set in the wrong YAML level is ignored silently; check runresults.json to confirm failures were actually stored.
• Copying a whole model header into a test also imports materialization keys that tests cannot honor; strip everything except the query.
• A test defined in a package may need the fix applied in the package, not overridden locally by copying it.

Provenance

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

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

Thread query: Compilation Error: 'config' is undefined in test definition

TL;DR: Generic test definitions do not get the model config function. Move the settings into the test YAML arguments or into the test SQL itself: set severity and thresholds as test arguments in schema.yml, and drop the config call from the test file. The test then parses and runs with the intended severity.

Not specified by the original author.

TL;DR

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. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York

Use this when

• You see this exact message or symptom in Grafana: dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Grafana fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the panel query and its data frame shape, the dashboard uid and folder, the data source plugin installation, and the service account role on the folder, and check the live object state, the config value, and the first place the two disagree. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: 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. Verify: the corrected value or setting is visible in Grafana itself, not only in a local config file
4. Re-run the original operation on the single affected item first: save a copy of the dashboard under a test uid, fix the panel or provisioning entry, then promote the corrected dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Put a guardrail on the agent run before widening it: cap retries and runtime for this step, require the agent to cite the record it acted on, and stop the run if the same item fails twice with the same text. Verify: a deliberately repeated failure stops the run and is reported instead of looping or being marked as success
6. Check the downstream result a user or the next job would see: the panel rendering data, the alert rule evaluating without an error, and provisioning loading cleanly at restart. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
7. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Grafana version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Grafana 10 or 11, provisioned dashboards, unified alerting, data source plugins. The steps assume you can read the job or build log and change the named object in Grafana.

Why it happens

In Grafana, this failure usually means the stored configuration describes the intended setup while the live system has drifted from it. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

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

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

Thread query: dashboard agent mis-mapped timezone in Grafana panel: agent set UTC while source data was America/New_York

TL;DR: 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. Start in the Grafana dashboard page, the alerting evaluation log, and the provisioning folder, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Not specified by the original author.

TL;DR

The var was never defined, so dbt has nothing to substitute. Define it in dbtproject.yml under vars, pass it with --vars on the command line, or give the var() call a default like var('myvar', 'fallback'). Pick one; the default argument is the quickest unbreak.

Error

Compilation Error: var is undefined in dbt model

Steps

1. Find the var call in your model: search for var('name') matching the undefined name in the error. Expected: You locate the exact line and the var name dbt complains about.

2. Check dbt_project.yml for a vars: block defining it, and check whether your run passes --vars '{name: value}'. One of these is missing. Expected: You confirm the var is defined nowhere, or only defined for a different target.

3. Fix it: add it under vars: in dbtproject.yml, or change the call to var('name', 'sanedefault') so it degrades gracefully. Expected: The var resolves; you can verify with dbt compile and inspect the rendered SQL in target/compiled.

4. Run dbt compile --select the model, then a full dbt compile to catch other models using the same var. Expected: Whole project compiles with no undefined-var errors.

When to use

• Compilation Error names a var as undefined
• a model works for one target but fails for another (vars differ per target)
• a new model copied a var() call from elsewhere without the definition

When not to use

• the error is about env_var, not var (that is an environment variable, different fix)
• the var is defined but has the wrong value (that is a config bug, not undefined)
• the failure happens at warehouse runtime, after successful compile

Tool compatibility

• dbt-core 1.0 and later; --vars CLI flag syntax unchanged
• dbt Cloud: set vars in the job's deployment environment or job settings
• dbt_project.yml vars block works across all adapters

Variant phrasings

var is undefined only in CI

CI runs dbt without the --vars flag your local alias includes. Put the var in dbt_project.yml instead of relying on local shell aliases.

var undefined inside a macro

Same fix, but check the macro is not called before vars load. Macro-level var() calls resolve fine as long as the var is defined project-wide.

Why it happens

var() is dbt's project-level variable lookup. If the name is not in dbt_project.yml vars and not passed via --vars, there is nothing to return and dbt raises at compile time rather than rendering an empty string. Copy-paste between projects is the usual way the definition gets lost.

Edge cases

• vars: defined under a target-specific block only apply to that target; a model compiled for prod will not see dev-only vars.
• Watch quoting: --vars '{my_var: abc}' needs the braces quoted or the shell eats them.

Provenance

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

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

Thread query: Compilation Error: var is undefined in dbt model

TL;DR: The var was never defined, so dbt has nothing to substitute. Define it in dbtproject.yml under vars, pass it with --vars on the command line, or give the var() call a default like var('myvar', 'fallback'). Pick one; the default argument is the quickest unbreak.