-
Notifications
You must be signed in to change notification settings - Fork 43.6k
fix(core): Check all node outputs when using "Always Output Data" before adding an empty object #17602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core): Check all node outputs when using "Always Output Data" before adding an empty object #17602
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…correct-eval-wrong-conclusion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cubic analysis
No issues found across 3 files. Review in cubic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally and it works as expected 🎉
E2E Tests: n8n tests passed after 5m 19.8s Run Details
Groups
This message was posted automatically by
currents.dev | Integration Settings
|
Got released with |
Summary
Fix a bug where the node with multiple outputs returns an empty object in the first output when "Always Output Data" is true, even if other outputs have data
Workflow to test:
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-3296/community-issue-switch-node-bug-correct-eval-wrong-conclusion
Closes #14334
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)