---
title: "Fusion Missing Features"
source: dbt Core Documentation
source_url: https://github.com/dbt-labs/docs.getdbt.com
licence: Apache-2.0
domain: data-and-analysis
subdomain: dbt-docs
date_added: 2026-04-25
---

| Feature | This will affect you if... | GitHub issue |
|---------|----------|---------|
| [--warn-error, --warn-error-options](/reference/global-configs/warnings)      | You are upgrading all/specific warnings to errors, or silencing specific warnings, by configuring the warning event names. Fusion's logging system is incomplete and unstable, and so specific event names are likely to change. | [dbt-fusion#8](https://github.com/dbt-labs/dbt-fusion/issues/8) |
| Iceberg support (BigQuery)   | You have configured models to be materialized as Iceberg tables, or you are defining `catalogs` in your BigQuery project to configure the external write location of Iceberg models. Fusion doesn't support these model configurations for BigQuery. | [dbt-fusion#947](https://github.com/dbt-labs/dbt-fusion/issues/947) |
| [Model-level notifications](/docs/deploy/model-notifications)                 | You are leveraging the dbt platform’s capabilities for model-level notifications in your workflows. Fusion currently supports job-level notifications. | [dbt-fusion#1103](https://github.com/dbt-labs/dbt-fusion/issues/1103) |
| [dbt-docs documentation site](/docs/build/view-documentation#dbt-docs) and ["docs generate/serve" commands](/reference/commands/cmd-docs)  | Fusion does not yet support a local experience for generating, hosting, and viewing documentation, as dbt Core does via dbt-docs (static HTML site). We intend to support such an experience by GA. If you need to generate and host local documentation, you should continue generating the catalog by running dbt docs generate with dbt Core.  | [dbt-fusion#9](https://github.com/dbt-labs/dbt-fusion/issues/9) |
| [Programmatic invocations](/reference/programmatic-invocations) | You use dbt Core’s Python API for triggering invocations and registering callbacks on events/logs. Note that Fusion’s logging system is incomplete and unstable. | [dbt-fusion#10](https://github.com/dbt-labs/dbt-fusion/issues/10) |
| [Linting using SQLFluff](/docs/deploy/continuous-integration#to-configure-sqlfluff-linting) | You use SQLFluff for linting in CI or local development. SQLFluff is not natively compatible with the <Constant name="fusion_engine"/>. Support varies by where you run it: **<Constant name="dbt_platform"/> CI jobs**: SQLFluff linting is not available when running on <Constant name="fusion"/>. **Studio IDE**: SQLFluff linting works, but uses the <Constant name="core"/> engine templater rather than <Constant name="fusion"/>. **Local development**: You can run SQLFluff locally using the standalone <Constant name="core"/> engine templater as a workaround. A native <Constant name="fusion"/> linter is planned for a future release. | [dbt-fusion#11](https://github.com/dbt-labs/dbt-fusion/issues/11) |
| [`{{ graph }}`](/reference/dbt-jinja-functions/graph) - `raw_sql` attribute (for example, specific models in [dbt_project_evaluator](https://hub.getdbt.com/dbt-labs/dbt_project_evaluator/latest/)) | You access the `raw_sql` / `raw_code` attribute of the `{{ graph }}` context variable, which Fusion stubs with an empty value at runtime. If you access this attribute, your code will not fail, but it will return different results. This is used in three quality checks within the [`dbt_project_evaluator` package](https://hub.getdbt.com/dbt-labs/dbt_project_evaluator/latest/). We intend to find a more-performant mechanism for Fusion to provide this information in the future. | Coming soon |
