What causes ModelConfigError?

An unrecognized materialization type (e.g., a typo in materialized='tabel'). An invalid partition_by or cluster_by configuration for the target warehouse. An invalid tags value (must be a string or list of strings). A post-hook or pre-hook that contains invalid SQL. An invalid contract configuration (enforce: true without column definitions)

How do I fix ModelConfigError?

Read the error message — dbt usually names the specific model and configuration key that is invalid. Check the config() block in the model SQL file for typos. Verify the configuration key is supported for the adapter being used (BigQuery, Snowflake, Databricks, etc.). Run dbt compile --select to validate the model configuration without executing. Check the dbt documentation for the valid values for the configuration key

Medium severityconfiguration

Power BI Refresh Error:
ModelConfigError

What does this error mean?

A dbt model has an invalid configuration — either in its config() block, in schema.yml, or in dbt_project.yml. dbt cannot compile or run the model.

Common causes

1An unrecognized materialization type (e.g., a typo in materialized='tabel')
2An invalid partition_by or cluster_by configuration for the target warehouse
3An invalid tags value (must be a string or list of strings)
4A post-hook or pre-hook that contains invalid SQL
5An invalid contract configuration (enforce: true without column definitions)

How to fix it

1Read the error message — dbt usually names the specific model and configuration key that is invalid
2Check the config() block in the model SQL file for typos
3Verify the configuration key is supported for the adapter being used (BigQuery, Snowflake, Databricks, etc.)
4Run dbt compile --select <model> to validate the model configuration without executing
5Check the dbt documentation for the valid values for the configuration key

Frequently asked questions

Where can model configuration be defined?

In three places: the config() block in the model SQL file, the model's entry in schema.yml, or the models: key in dbt_project.yml. All three are merged, with the config() block taking highest precedence.

Is the materialization='incremental' config the same across all adapters?

The materialization name is the same, but the supported strategy values differ by adapter. For example, merge is supported on Snowflake and BigQuery but not on Postgres (which uses delete+insert).