Skip to content
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

Start Node could not be deleted. #379

Closed
naishweb opened this issue Mar 15, 2020 · 2 comments
Closed

Start Node could not be deleted. #379

naishweb opened this issue Mar 15, 2020 · 2 comments

Comments

@naishweb
Copy link

naishweb commented Mar 15, 2020

When i am using a trigger, the workflow will not begin the execution at the trigger, it begins at the "Start"-node.

  1. I cant remove the Starting node (it doesn't matter if the node is active or not)
  2. The workflow does not begin with the trigger node, it begins with the starting node.

To Reproduce
Steps to reproduce the behavior:

  1. fresh docker latest image
  2. Create new Workflow
  3. Add Trigger Node of choice
  4. Trashcan symbol of startnode does not delete the start node
    4.a [optional] press the pause icon from the start button
  5. press "Execute Workflow"
  6. workflow will begin executing @ "Start" Node

Expected behavior
I assume that the trigger is the starting point of the workflow. Therefore i want to delete the "Start"-node but the trashcan-symbol does not fullfill this operation

Environment (please complete the following information):

  • latest docker image [
  • n8n Version [0.55.1]
  • Node.js Version [12.13.0]
    ]
@janober
Copy link
Member

janober commented Mar 16, 2020

Ah yes, that behavior is as expected. Each workflow has to contain a Start-Node, so it can not be deleted.

Also, the way it executes was planned that way. If it should get executed differently then the "Play-Button" of the last node of the branch which should be executed can be pressed. It will then find the first node of this branch and executes starting from there. I can, however, understand that it is maybe confusing for beginners and so just changed the default behavior to look first if there is a Trigger-Node in the flow and if yes, it chooses the very first one it finds as starting point. Only if no Webook-Node or Trigger-Node can be found will it start to execute from the Start-Node.

Will be released with the next version.

And the next time please post to the forum first as Github-Issues are only for confirmed bugs. Thanks!

@janober janober closed this as completed Mar 16, 2020
@janober
Copy link
Member

janober commented Mar 17, 2020

Got released with n8n@0.56.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants