[Redshift] on-run-end failure: cannot insert multiple commands into a prepared statement

[SkinnyPigeon]

Describe the bug
Starting this morning, Elementary began to fail during its on-run-end hook:

[2025-12-01, 08:31:50 UTC] {docker.py:429} INFO - �[0m08:31:50  Running 1 on-run-end hook
[2025-12-01, 08:31:53 UTC] {docker.py:429} INFO - �[0m08:31:53  Database error while running on-run-end
[2025-12-01, 08:31:53 UTC] {docker.py:429} INFO - �[0m08:31:53
[2025-12-01, 08:31:53 UTC] {docker.py:429} INFO - �[0m08:31:53  Finished running 1 table model, 1 project hook in 0 hours 4 minutes and 4.23 seconds (244.23s).
[2025-12-01, 08:31:54 UTC] {docker.py:429} INFO - �[0m08:31:54
[2025-12-01, 08:31:54 UTC] {docker.py:429} INFO - �[0m08:31:54  �[31mCompleted with 1 error and 0 warnings:�[0m
[2025-12-01, 08:31:54 UTC] {docker.py:429} INFO - �[0m08:31:54
[2025-12-01, 08:31:54 UTC] {docker.py:429} INFO - �[0m08:31:54    on-run-end failed, error:
 cannot insert multiple commands into a prepared statement
[2025-12-01, 08:31:54 UTC] {docker.py:429} INFO - �[0m08:31:54
[2025-12-01, 08:31:54 UTC] {docker.py:429} INFO - �[0m08:31:54  Done. PASS=1 WARN=0 ERROR=1 SKIP=0 TOTAL=2

Looking in the Elementary Slack community, it appears that there are a few of us who have all started encountering this in the last few days.

One community member suggested a fix in the thread linked above.

We have currently disabled Elementary as it appears it was affecting all of our pipelines. Could you please give this a look, and at least confirm if the suggested macro overwrite would be a safe-to-use workaround for the time being?

Thanks

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Elementary CLI (edr) version: [e.g. 0.5.3], can be found by running pip show elementary-data
• Elementary dbt package version: [e.g. 0.4.1], can be found in packages.yml file
• dbt version you're using [e.g. 1.8.1]
• Data warehouse [e.g. snowflake]
• Infrastructure details (e.g. operating system, prod / dev / staging, deployment infra, CI system, etc)

Additional context
Add any other context about the problem here.

Would you be willing to contribute a fix for this issue?
Let us know if you're willing to contribute so that we'll be able to provide guidance.

[sarojts]

We are also facing the same issue from yesterday, but for same elementary version it was working before. Whole prod is failing now.

[sudhanshurawat80-maker]

Adding below var in dbt project helped us suppress the issue.

elementary:
disable_dbt_artifacts_autoupload: true

[clagali-movable]

For us the following vars helped in suppressing the issue as a temporary measure.

vars:
  elementary:
      disable_run_results: true
      disable_dbt_artifacts_autoupload: true
      disable_dbt_invocation_autoupload: true

[SkinnyPigeon]

Thanks. We just disabled the whole thing in prod by removing it from the enabled list:

  elementary:
    +schema: "elementary"
    enabled: "{{ target.name in ['beta'] }}"

[NoyaOffer]

Hey everyone, thanks for bringing this to our attention, we'll take a look to see what's going on.
For now, as mentioned, we recommend disabling the autoupload and try uploading the Elementary artifacts in a separate run - see the full guide here.

Please let us know if you're able to update the Elementary tables outside of the on-run-end hook.

We'll share an update as soon as we have one!

[NoyaOffer]

elementary-data/dbt-data-reliability#899
The fix will be released in a couple of days 🙌

[clagali-movable]

Thanks @NoyaOffer for the kind update. Will the fix be released to all versions of elementary or will it be a part of the most recent release?
We are currently on elementary version 0.19.0.
Would we need to upgrade to the latest version of elementary to use the fix? and which version would that be?

[karthickGK4794]

elementary-data/dbt-data-reliability#899 The fix will be released in a couple of days 🙌

is this resolved? because we still see this issue

[phillip-burger-sculpturearts]

Noting that I have encountered this issue in my environment. Started last night. Other member on my team cannot re-create in their development environment. When I disabled elementary, issue did not occur. Redshift. Package elementary 0.17.0 and 0.20.1. Encountered on dbt Cloud and dbt-core 1.10.13 in Cursor. is not occurring in production dbt job that runs on dbt Cloud.

Cursor DB plugins:

  - redshift: 1.9.5 - Up to date!
  - postgres: 1.9.1 - Up to date!

Observed this morning an additional log entry I did not see last night:

17:03:34 Observability Metric: command_success=0.0: Database Error
  cannot insert multiple commands into a prepared statement

[NoyaOffer]

Done and released in Elementary 0.21.0! Thanks everyone for surfacing this.

[FridayPush]

Updated to 0.21.0 and we continue to see this error. Detailed logs show it on deleting two test tables:

...
2025-12-16 00:02:29.405766 (MainThread): 00:02:29  Elementary: Runtime data: {"config": {}, "dbt_version": "2025.12.15+44d5161", "elementary_version": "0.21.0", "database": "db", "schema": "elementary"}
...

/* --ELEMENTARY-METADATA-- {"command": "build", "invocation_id": "d4501589-c827-46cc-b9c7-bc48203c43bc", "package_name": "elementary", "resource_name": "elementary-on-run-end-0", "resource_type": "operation"} --END-ELEMENTARY-METADATA-- */
    
        BEGIN TRANSACTION;
        
            DROP TABLE IF EXISTS "marts"."elementary"."test_1396fa6431_elementary_source_table_anomalies_customers_row_count__metrics__tmp_20251216000237994812";
        
            DROP TABLE IF EXISTS "marts"."elementary"."test_1396fa6431_elementary_source_table_anomalies_customers_row_count__anomaly_scores__tmp_20251216000253260282";
        
        COMMIT;
2025-12-16 00:04:31.976664 (MainThread): 00:04:31  Redshift adapter: Redshift error: cannot insert multiple commands into a prepared statement
2025-12-16 00:04:31.978305 (MainThread): 00:04:31  Redshift adapter: Not retrying error: Database Error
  cannot insert multiple commands into a prepared statement

[danielhorvath-cleo]

@NoyaOffer Same as @FridayPush , we just upgraded to 0.21.0 specifically to solve this, yet we are seeing the same problem, exactly as described above.

There are multiple DROP TABLE IF EXISTS ... statements within one transaction that causes the failure.