Issue with default workflow loading persistence after updates #11494
Description
Custom Node Testing
- I have tried disabling custom nodes and the issue persists (see how to disable custom nodes if you need help)
Your question
I am very disappointed. Every time an update is released, the method for loading the default startup workflow changes. I cannot update without constantly modifying my startup wrapper.
It honestly feels like a deliberate attempt to make things difficult. The logic is now buried so deep that patching the file to load my custom workflow has become overly complicated, if not impossible.
Please provide a stable solution or a consistent entry point for custom workflows.
Logs
Other
No response