Some models are not materialized

When processing your dbt project, Colibri may report that some models are “not materialized (missing from catalog).” This means those models exist in your manifest.json but have no matching entry in catalog.json.

Why does this happen?

• The model was never run against the warehouse (e.g., a new model that hasn’t been materialized yet).
• The model uses the ephemeral materialization strategy, so it never creates a physical table or view.
• The catalog.json was generated before the model was created, for example, running dbt docs generate before dbt run.

What does this affect?

Models missing from the catalog will still appear in your lineage graph at the table level, but column-level lineage will not be available for those models. Colibri needs catalog information (column names, data types) to trace column-level dependencies.

How to fix it

Ensure your models are materialized in the warehouse and regenerate the catalog:

dbt run
dbt docs generate

Then re-upload or re-sync your artifacts. For CI/CD pipelines, make sure dbt docs generate runs after dbt run so the catalog reflects the latest state of your warehouse.

If the issue persists, please raise a bug report .