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

The Execute Workflow node is disappeared from default nodes #5579

Closed
AFirouzi opened this issue Feb 28, 2023 · 3 comments
Closed

The Execute Workflow node is disappeared from default nodes #5579

AFirouzi opened this issue Feb 28, 2023 · 3 comments
Labels
in linear Issue or PR has been created in Linear for internal review

Comments

@AFirouzi
Copy link

Describe the bug
When the user searches for the Execute Workflow node to add it to the workflow, the search results only include the Execute Workflow Trigger.
However, it is still possible to have it in the workflow by copying from another workflows but not using the search option.

To Reproduce

  1. Go to Workflows Tab on the left side bar.
  2. Click on Add Workflow
  3. Click on the + sign on the top right corner
  4. Search for the Execute Workflow
  5. The Execute Workflow node is not showing in the results.

Expected behavior
The user can find the Execute Workflow in the search results from the default nodes.

Environment (please complete the following information):

  • OS: Windows
  • n8n Version: 0.217.0
  • Node.js Version: 16.18.1
  • Database system PostgreSQL
  • Operation mode: own
@Joffcom
Copy link
Member

Joffcom commented Feb 28, 2023

Hey @AFirouzi,

Thanks for reporting this one, This is being tracked internally as ADO-404 and can also be found on the community support forum here: https://community.n8n.io/t/execute-workflow-node-missing/23418

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Feb 28, 2023
@Joffcom Joffcom added the Upcoming Release Will be part of the upcoming release label Feb 28, 2023
@Joffcom
Copy link
Member

Joffcom commented Feb 28, 2023

Hey @AFirouzi,

The fix for this has just been merged so this will resolved in the next release, I am going to mark this one as closed but you will get a notification here once the release is available.

@Joffcom Joffcom closed this as completed Feb 28, 2023
@janober
Copy link
Member

janober commented Mar 2, 2023

Fix got released with [email protected]

@janober janober removed the Upcoming Release Will be part of the upcoming release label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review
Projects
None yet
Development

No branches or pull requests

3 participants