The error message

Encountered an error while running operation: Database Error 'Macro' object has no attribute 'config'

suggests that there is a compatibility issue between the dbt version, the adapter (in your case, dbt-databricks), and the Elementary package. A very similar error has been reported in the context of other adapters (e.g., Trino), where the root cause was a breaking change in dbt or the adapter, or a macro incompatibility in the Elementary package. For example, a user running dbt 1.8.8 and Elementary 0.17.0 with Trino encountered

'dict object' has no attribute 'config'

in a macro call stack, which was traced to incompatibility between the dbt/adapter version and the Elementary package version. The Elementary team requested details about the dbt and Elementary versions and whether this was a first-time run or a recent breakage, indicating that such errors are often version-related and may require a fix in the package or an update to the macros to match the latest dbt API changes. The issue was not resolved in the thread, but the context is highly similar to your situation with Databricks and dbt 1.9.x [Slack thread: Trino macro error](https://slack.com/archives/C02CTC89LAX/p1741344297909659). What you can try: - Ensure that your Elementary dbt package version matches your CLI version (0.18.3) and is compatible with dbt-core 1.9.4 and dbt-databricks 1.10.3. - If you recently upgraded dbt or the adapter, check the [Elementary release notes](https://docs.elementary-data.com/release-notes/upgrading-elementary) for compatibility guidance. - If you override any core dbt macros (such as

ref()

), this can also cause macro attribute errors, as seen in another thread. If so, try disabling or reverting those overrides to see if the error persists [Slack thread: MacroGenerator object has no attribute 'config'](https://slack.com/archives/C02CTC89LAX/p1667235374261789). - If the issue persists, consider downgrading to a previous version of dbt or the adapter that is known to work with Elementary 0.18.3, or reach out to the Elementary community with your logs and configuration details for more targeted support. Unfortunately, the knowledge sources do not contain a confirmed fix for this exact error with your specific versions, but the evidence strongly points to a version or macro compatibility issue. If you provide more details (such as whether this is a new issue after an upgrade, or if you have custom macros), the Elementary team or community may be able to assist further.