Dashboard widgets inside subflows

The general question is whether ui widgets can work properly inside subflows. In particular, I want to use a ui_switch node in a subflow. Each subflow instance produces a widget in the dashboard that operates independently, but they do not appear in the order I want. The dashboard tab in the editor shows only one node, so I don't see an obvious way to re-arrange the dashboard widgets. Is there a workaround? What determines the order in which the widgets appear? Should I look for a different way to clean up my flows?

Correct - you cannot use dashboard widgets inside subflows for exactly the layout reason you identify. The sidebar that controls the layout order knows nothing about subflows so there is no current workaround.

I have the same problem, would be nice to have this working... the flows could be simplified a lot.
Maybe is a good idea if every widget is prefixed with the name of the sub-flow this way we can order them in right panel.
If this is not possible, at least to draw them in order, like drawing all with gets from each sub-flow and then get the next sub-flow and so on...

Another solution would be to offer the possibility to set the group from an environment parameter.
This way we can set the group on the sub-flow and take the group from there

My "work around" is to have the dashboard items send their messages with a very specific TOPIC.

Then in the sub-flow, I route those messages to the dashobard node.

I may be missing something, but I don't see how any of these suggestions resolves or works around the issue I described. The dashboard clearly knows about the distinct widgets inside each subflow instance, but the sidebar tab does not and so cannot arrange them properly. Changes would be needed in the editor to fix this. BTW, does anyone know whether the new (beta) dashboard layout editor does anything different. (The only machine I have running the beta is down right now.)

The layout editor doesn't change the (lack of) support for dashboard widgets in a subflow.

... but it is in the plan. Can't say when as I don't know when we'll get to work on it, but it has been discussed in some detail.