Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix WorkflowHasIssuesError from the test execution path swallows the actual node/field detail [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#29608•Fetched 2026-05-01 05:52:15
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Author
kenlyle2kenlyle2
Participants
bkauto3bkauto3kenlyle2kenlyle2n8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
commented ×2labeled ×1mentioned ×1subscribed ×1

Error Message

  1. Observe the execution error. Expected: Error message identifies the specific node and field causing the issue, e.g. Node "Airtable": Missing or invalid required parameters: table Note: The POST /api/v1/workflows/{id}/activate endpoint correctly returns the specific node and field in its error response. The test execution path has access to the same information and should surface it identically. Useful error reporting.
  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

WorkflowHasIssuesError from the test execution path swallows the actual node/field detail that the activate endpoint correctly surfaces, making it completely undebuggable for users.

To Reproduce

  1. Import any workflow JSON that contains at least one node with a missing required parameter (e.g. an Airtable node where the table field was not set or was cleared during editing).
  2. Ensure all credentials are properly configured and verified — the workflow shows no red marks in the canvas UI.
  3. Click the Webhook node → Listen for test event, then fire a POST request to the test webhook URL.
  4. Observe the execution error.

Expected: Error message identifies the specific node and field causing the issue, e.g. Node "Airtable": Missing or invalid required parameters: table

Actual: WorkflowHasIssuesError: The workflow has issues and cannot be executed for that reason. Please fix them first. — no node name, no field name, no actionable information.

Note: The POST /api/v1/workflows/{id}/activate endpoint correctly returns the specific node and field in its error response. The test execution path has access to the same information and should surface it identically.

Expected behavior

Useful error reporting.

Debug Info

Debug info

core

  • n8nVersion: 2.18.5
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 84f851e6-3cd4-4a39-b388-437e27bcf08b

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/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-30T23:41:33.004Z

Operating System

Ubuntu 24.04

n8n Version

2.18.5

Node.js Version

24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The test execution path should be updated to surface specific node and field details in the error message, similar to the activate endpoint.

Guidance

  • Review the error handling in the test execution path to ensure it includes the specific node and field details, as done in the activate endpoint.
  • Compare the error response from the activate endpoint with the error message in the test execution path to identify the missing information.
  • Update the test execution path to include the node name and field name in the error message, providing actionable information for users.
  • Verify the changes by reproducing the error and checking the error message for the expected details.

Example

No code snippet is provided as the issue does not include specific code references.

Notes

The issue seems to be related to the error handling in the test execution path, which does not provide sufficient information about the node and field causing the error. The activate endpoint correctly returns the specific node and field in its error response, which should be used as a reference for updating the test execution path.

Recommendation

Apply workaround: Update the test execution path to surface specific node and field details in the error message, as the issue is likely caused by incomplete error handling in this path.

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

Useful error reporting.

#api#LLM response#prompt template#agent execution#callback 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

n8n - 💡(How to fix) Fix WorkflowHasIssuesError from the test execution path swallows the actual node/field detail [2 comments, 3 participants]