Explanation:
You should use Move to top to force a single queued flow to run next. In the Power Automate portal, you can monitor the queues on each machine and machine group. You can use the Move to top action to bring the flow to the top of the queue so that it will run next when a machine becomes available.
You should edit cloud flow to change upcoming flow runs to High priority. The priority for desktop flows is set to either Normal or High in the cloud flow step that runs the desktop flow. To change the priority for all future runs of the desktop flow, you need to edit this step in the cloud flow and change its priority.
You should use Change priority to change a single queued flow run to High priority. Once a desktop flow run has been added to a queue you can change the priority set by its calling cloud flow. This only changes the priority for this run and does not affect future runs of the desktop flow.
You should not edit the desktop flow. The desktop flow does not contain its priority. The priority is set on the Run a flow built with Power Automate for desktop action in the cloud flow and can be overridden in the Power Automate portal when a desktop flow is queued.
You should not add a Machine group. Machine groups can be used to distribute desktop flows across computers. Each machine group can have its own queue and it can be beneficial to have a separate machine group with enough machines for business-critical desktop flows to run quickly.