n8n - 💡(How to fix) Fix Salesforce Node is not outputing full error in error node.

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…

Error Message

When the Salesforce node is used to create records, and "On Error" is set to "Continue (using error output)" then output does not contian details about the error. If you change it to On Error "Continue" it is also missing error details.

  1. Add a Salesforce record creation node and cause the error. The easiest option is to add an empty custom field in the node configuration
  2. Try different On Error behaviours to see differences in output. Full error returned from SF is passed as JSON to the error node.
  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When the Salesforce node is used to create records, and "On Error" is set to "Continue (using error output)" then output does not contian details about the error.

<img width="491" height="83" alt="Image" src="https://github.com/user-attachments/assets/486b1fe6-8f6c-48f9-9589-88a46d0a7bbc" />

If you change it to On Error "Continue" it is also missing error details.

<img width="347" height="87" alt="Image" src="https://github.com/user-attachments/assets/2637400c-3674-470e-9d50-b41746c50f44" />

Only when you set it to "Stop Workflow" you can see details

<img width="653" height="279" alt="Image" src="https://github.com/user-attachments/assets/66b22e84-4068-4d37-902d-8020337119bc" />

This is critical for debugging to see what exactly happened. Currently, we are blind on errors.

To Reproduce

  1. Add a Salesforce record creation node and cause the error. The easiest option is to add an empty custom field in the node configuration
<img width="362" height="127" alt="Image" src="https://github.com/user-attachments/assets/86177912-5f45-49d2-8ed9-558cb19512f8" />
  1. Try different On Error behaviours to see differences in output.
<img width="401" height="191" alt="Image" src="https://github.com/user-attachments/assets/c5a68205-aa90-45a1-89fa-4aca3b9d0c16" />

Expected behavior

Full error returned from SF is passed as JSON to the error node.

Debug Info

Debug info

core

  • n8nVersion: 2.17.7
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community
  • consumerId: unknown

storage

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

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

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

Generated at: 2026-05-20T10:14:43.702Z

Operating System

Windows 11

n8n Version

2.17.7

Node.js Version

24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

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

Full error returned from SF is passed as JSON to the error node.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING