HI Nick,
I am afraid I cannot share an example of a nonworking flow... I copied the keyboard flow, created a new Tab and imported the flow into the new Tab in a new group to test out the nonworking example to share... The only problem is that it worked the way it is supposed to. I checked the original flow and it was also working correctly. "Murphy's Law"... But I think I know what may have caused the problem; I had moved some Nodes from one Tab to another and one Group to another from within the template nodes. I don't think the Dashboard menu had quite cough up with the moves and updated the Dashboard menu correctly. When I created a new Tab I believe the issue corrected itself... I had noticed when I created the new Tab, it was on the bottom of the Dashboard menu but on the top of the UI Menu (the first on on the list). But when I moved one of the Tabs in the Dashboard, the UI menu corrected its order.
I had tried to recreate the issue and moved some Nodes from one Tab to another and back again, I noticed when I moved them back that the Nodes was at the bottom of the Dashboard Group... but again, in the UI they were at the top of the group. I moved the position of one of the nodes in the Dashboard menu and in the UI they all dropped down the bottom to the same order as the Dashboard.
I think possibly, if I would have moved the position of one of the Tabs, the malfunctioning deterministic system would have corrected itself. I think sometimes the Dashboard menu doesn't get correctly updated when moving nodes until you move one of the Tabs and the Dashboard menu then gets correctly updated...
Thanks, Steve