Issues with executing workflows manually are sadly expected. Especially if there are loops and other complicated constructs involved as the workflow actually has to first run backward (to figure out what nodes to execute) and then again forward.
It is for sure a bug that we should fix at some point but probably nothing I would honestly prioritize right now. Is something that is probably hard to fix and the chance that we destroy more than what we repair is quite high. We will however address that in the future as we rewrite part of that code in the future.
But that issues will not have any impact on the workflow executing correctly in production. It is currently “only” a limitation for testing it when executing nodes manually.
I can live with that Bug, especially as it doesn’t affect the production runs.
If it’s complicated and/or risky to fix, i would probably prefer more awesome new Features beeing build instead