- Notifications
You must be signed in to change notification settings - Fork36.2k
fix(core): Ensure error.message is a string before checking for specific messages#17417
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Conversation
CLAassistant commentedJul 17, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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 reviewed 9 files and found no issues. Review PR incubic.dev.
Hey@naXa777, Thanks for the PR, We have created "GHC-3171" as the internal reference to get this reviewed. One of us will be in touch if there are any changes needed, in most cases this is normally within a couple of weeks but it depends on the current workload of the team. |
Hey@naXa777, Please don't forget to add tests. |
Uh oh!
There was an error while loading.Please reload this page.
Summary
Fix "Workflow validation failed: e.message.includes is not a function" error by ensuring
error.message
is a string before calling.includes
. This issue occurs during workflow validation, but it's unclear whether the root cause is inn8n orn8n-mcp (workflow-validator.ts).Added a defensive type check to avoid runtime failures.
Related Linear tickets, Github issues, and Community forum posts
fixes#17413.
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)