Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Workflow auto-deactivates after BigQuery Insert node crash despite successful data write [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#29602•Fetched 2026-05-01 05:52:22
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Author
leandrobacacastexleandrobacacastex
Participants
bkauto3bkauto3leandrobacacastexleandrobacacastexn8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×2labeled ×1mentioned ×1subscribed ×1

Error Message

Actual behavior: Execution marked as error post-insert, workflow auto-deactivates.

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

n8n version: 1.123.33 Description: After a BigQuery "Insert rows in a table" node executes successfully (data is written to the table), the workflow crashes and n8n marks the execution as failed. After multiple occurrences, n8n automatically deactivates the workflow. Expected behavior: Workflow completes successfully after data is written. Actual behavior: Execution marked as error post-insert, workflow auto-deactivates. Steps to reproduce:

Workflow fetches data from external API Transforms data with Code node Inserts rows into BigQuery table Execution fails after insert despite data being written

Additional context: Data arrives correctly in BigQuery. Issue is with n8n's handling of the BigQuery node response.

To Reproduce

  1. Create a workflow with: Schedule Trigger > HTTP Request (Prometheo API) > Code node (Transform) > BigQuery "Insert rows in a table" node
  2. Execute the workflow
  3. Data is written successfully to BigQuery
  4. Execution is marked as failed/crashed despite successful insert
  5. After multiple occurrences, n8n auto-deactivates the workflow

Expected behavior

Workflow completes successfully after BigQuery insert. Execution marked as success.

Debug Info

Debug info

core

  • n8nVersion: 1.123.33
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-30T18:25:53.727Z

Operating System

n8n cloud

n8n Version

1.123.33

Node.js Version

24.13.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The workflow execution fails after a successful BigQuery insert due to n8n's handling of the BigQuery node response, suggesting a potential issue with error handling or response parsing.

Guidance

  • Verify the BigQuery node's response to ensure it matches n8n's expected format, as the issue seems to be related to n8n's handling of the response.
  • Check the n8n logs for any error messages or warnings that may indicate the cause of the failure, focusing on the time frame after the BigQuery insert.
  • Review the Code node's transformation logic to ensure it does not inadvertently cause the workflow to fail after the BigQuery insert.
  • Consider adding error handling mechanisms, such as try-catch blocks, around the BigQuery node to catch and handle any potential errors that may be causing the workflow to fail.

Notes

The provided information suggests that the issue is specific to the interaction between n8n and the BigQuery node, but without more detailed logs or error messages, it's challenging to provide a precise solution.

Recommendation

Apply workaround: Implement error handling around the BigQuery node to catch and handle potential errors, allowing the workflow to continue executing even if the BigQuery insert response is not as expected.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Workflow completes successfully after BigQuery insert. Execution marked as success.

#api#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING