-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Bug with Sticky notes created via API #9174
Comments
Hey @barn4k, The issue here appears to be that you have given the sticky notes the same name and we expect node names to be different even for sticky notes. If you set the name for the second sticky note to |
Oh, that's an interesting part. Maybe there should be an error raised when the same name is being used for different nodes. Or to make n8n automatically add 1,2,3 postfixes like it does in the UI |
Hey @barn4k, Those are not bad ideas, How did you make the workflow in the first place are you trying to build them by hand? |
@Joffcom The issue has been raised due to some workflows could have other notes, so that's why the sticky issue has happened. |
Bug Description
Seems if there are two sticky notes in one workflow created via API, one will disappear and the other one will be bugged. it won’t be possible to move it or edit unless you delete it (once). But after you have pressed the deletion button, the note will remain in its place. And now it will be movable and editable. The issue won’t happen if you edit the current sticky node via API, so it seems something messy is happening when there is no ID for the sticky notes defined
To Reproduce
Workflow:
Expected behavior
There will be two different sticky notes. Both are editable and movable.
Operating System
cloud
n8n Version
1.37.3
Node.js Version
cloud
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: