Runtime Error db05d03b When Writing to MotherDuck with dbt – Requesting Support on Commit Failure

Hi! I'm trying to determine whether this is an issue with my setup or an internal MotherDuck issue. I'm using:

When connected to MotherDuck, any write operation fails with:

Runtime Error
TransactionContext Error: Failed to commit: You've encountered an internal MotherDuck error.
Error ID: db05d03b

This occurs even with a minimal dbt model:

{{ config(materialized='table') }}

select 1 as id

Things I've already verified:

dbt compile succeeds.
The SQL executes successfully in the dbt Power User preview.
The failure occurs during COMMIT, not SQL compilation.
Switching the same project to a local DuckDB database removes the commit error. Local DuckDB instead reports expected S3 credential errors, suggesting the project itself is valid.

Could you check whether the error ID (db05d03b) corresponds to an internal service issue or if there's something I should change in my configuration?

Hi! I'm trying to determine whether this is an issue with my setup or an internal MotherDuck issue. I'm using:

When connected to MotherDuck, any write operation fails with:

Runtime Error
TransactionContext Error: Failed to commit: You've encountered an internal MotherDuck error.
Error ID: db05d03b

This occurs even with a minimal dbt model:

{{ config(materialized='table') }}

select 1 as id

Things I've already verified:

dbt compile succeeds.
The SQL executes successfully in the dbt Power User preview.
The failure occurs during COMMIT, not SQL compilation.
Switching the same project to a local DuckDB database removes the commit error. Local DuckDB instead reports expected S3 credential errors, suggesting the project itself is valid.

Could you check whether the error ID (db05d03b) corresponds to an internal service issue or if there's something I should change in my configuration?