-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Unable to enable workflow: "Validation Failed" #12296
Comments
Hey @wdhdev, Did you copy the node from another workflow or did you add it from the node panel? |
I copied it to another workflow because the original one was not working. Should I try creating them brand new? |
Unable to Enable Workflow: "Validation Failed I’m experiencing an issue when trying to enable a workflow in the application. Upon clicking the enable button, an error message appears stating "Validation Failed". The workflow cannot be activated, and I am unsure what is causing the problem. Steps to Reproduce: Open the application and navigate to the workflows section. Actual Behavior: Environment: Application Version: (e.g., 1.5.3) The issue persists even after restarting the application. Rechecked all workflow configurations. |
Bug Description
When I attempt to enable my workflow which uses a GitHub trigger, it returns
Workflow could not be activated: Validation Failed
even though it is valid and was working fine before.To Reproduce
Here is a screenshot of my workflow:
Note: When I run "test step" individually on each step one by one, the workflow works completely as expected, so I am unsure of the issue here as the error message is super vague and provides zero context.
I can export the workflow if needed, but I would rather not do it publicly due to some sensitive information being shown in the export.
I think this issue may be related to #10074.
Expected behavior
The workflow should activate and run fine.
Operating System
Debian 12.8
n8n Version
1.71.3
Node.js Version
20.18.0
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: