Error when running a workflow with missing node that is disconnected from the main graph
Open
Feature
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
### Feature Idea
When I run a workflow that is not connected to the main graph that has my SaveImage node, it still prevents the execution of the workflow. This is an annoying and arbitrary restrictions which puts barriers and extra steps into my work environment. If there is no mechanism to determine what is the "main graph" then please add an option in the error popup to ignore and continue, acting as if the nodes were disabled/silenced (CTRL-M) along with a permanent option.
### Existing Solutions
_No response_
### Other
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.