You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/desktop-flows/actions-reference/runflow.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: kewaiss
5
5
ms.service: power-automate
6
6
ms.subservice: desktop-flow
7
7
ms.topic: reference
8
-
ms.date: 01/31/2025
8
+
ms.date: 09/04/2025
9
9
ms.author: nimoutzo
10
10
ms.reviewer: matp
11
11
contributors:
@@ -21,21 +21,22 @@ search.audienceType:
21
21
22
22
The **Run desktop flow** action enables you to call other desktop flows while running a specific desktop flow. To use the action, add it to the workspace and select the desktop flow you want to call. If the called flow contains input variables, the action will prompt you to enter their values.
23
23
24
-
You can disable the toggle property 'Wait for flow to complete', which is enabled by default. If disabled, the invoked desktop flow runs concurrently with the parent flow. This configuration is useful for scenarios where unexpected popups in the target application block the parent flow. By running a child flow in parallel, you can monitor and manage these popups, ensuring the parent flow continues smoothly. This improvement provides a workaround given the current concurrency policy, which allows only one flow per machine at a time.
24
+
You can disable the toggle property 'Wait for flow to complete', which is enabled by default. If disabled, the invoked desktop flow runs concurrently with the parent flow. This configuration is useful for scenarios where unexpected popups in the target application block the parent flow. By running a child flow in parallel, you can monitor and manage these popups, ensuring the parent flow continues smoothly. This improvement provides a workaround given the current concurrency policy, which allows only one flow to run per machine at a time.
25
25
26
26
>[!IMPORTANT]
27
27
>
28
-
> - Only one parallel flow can run at this time. If a second child flow runs in parallel, an error occurs during runtime.
28
+
> - Up to six parallel flows in total can run concurrently with the root flow, shifting the previous limit of just one parallel flow.
29
+
> - Child flows can also run other child flows in parallel (no error is thrown in such cases anymore), consuming from the available pool of six parallel flows. Parallel flow runs are no longer limited to being invoked directly from the parent (root) flow, as was previously the case.
29
30
> - If a child flow runs in parallel, its output variables are ignored. The variables produced from the 'Run desktop flow' action aren't shown in the action modal.
30
-
> -Child flows can't run another child flow in parallel. A parallel flow run is allowed only if invoked directly from the parent (root) flow.
31
+
> -When a parent flow completes its run or is stopped, it also stops (cancels) its invoked parallel child flows that might still run.
31
32
32
33
To find more information about how to use the **Run desktop flow** action, go to [Run desktop flow from other desktop flows](../how-to/run-desktop-flow-action.md).
33
34
34
35
>[!NOTE]
35
36
>
36
37
> - A flow's dependencies can't be more than 150 other flows.
37
38
> - Two flows can't directly or indirectly call one-another as this causes a recursion.
38
-
> - In org tenants, the flows must be under the same environment.
39
+
> - In organization tenants, the flows must be under the same environment.
39
40
40
41
:::image type="content" source="media/runflow/run-desktop-flow-action-with-parallel-run-toggle.png" alt-text="Screenshot of the Run desktop flow action.":::
Tags are available in the Power Automate for desktop console to help you categorize and group desktop flows. Tags are custom text labels that let you organize your flows and manage them efficiently.
22
22
23
-
Tags are available (in preview) in the Power Automate for desktop console to help you categorize and group desktop flows. Tags are custom text labels that let you organize your flows and manage them efficiently.
The **Tags (Preview)** column displays all the tags that are associated with a desktop flow. To manage tags, such as adding or removing them for a flow, select **Manage tags (Preview)** in its context menu in the console. Alternatively, open the **Flow properties** pane and go to the **Tags (preview)** section.
23
+
The **Tags** column displays all the tags that are associated with a desktop flow. To manage tags, such as adding or removing them for a flow, select **Manage tags** in its context menu in the console. Alternatively, open the **Flow properties** pane and go to the **Tags** section.
28
24
29
25
In this section, add your preferred tags to the selected flow by selecting a tag from the list or creating a new text label. As you type, the list of tags in your environment automatically filters to help you choose an existing tag or create a new one. From the same pane, you can remove any tags previously associated with your flow. Select **Save** in the flow properties for the tag changes to take effect.
30
26
@@ -34,20 +30,22 @@ In this section, add your preferred tags to the selected flow by selecting a tag
34
30
35
31
## Update tags for multiple flows
36
32
37
-
Select multiple desktop flows and update their tags at the same time by selecting the common context option **Manage tags (Preview)**. A dialog appears, displaying only the tags already associated with all the selected flows. Remove common tags or add new ones associated with all selected flows.
33
+
Select multiple desktop flows and update their tags at the same time by selecting the common context option **Manage tags**. A dialog appears, displaying only the tags already associated with all the selected flows. Remove common tags or add new ones associated with all selected flows.
38
34
39
35
> [!NOTE]
40
36
> Tags associated with only a subset of the selected flows aren't displayed in this dialog and can't be removed this way.
41
37
42
38
## Filter flows based on tags
43
39
44
-
Select the **Filters** button in the console, and then select **Tags (Preview)** to filter your flows based on the tags you choose from the list. If you select two or more tags, there are two filtering modes:
40
+
Select the **Filters** button in the console, and then select **Tags** to filter your flows based on the tags you choose from the list. If you select two or more tags, there are two filtering modes:
45
41
46
42
-**Or**: Shows all flows that contain at least one of the selected tags.
47
43
-**And**: Shows only flows that contain all the selected tags.
48
44
49
45
Select **Clear** to reset the selected tags quickly.
50
46
47
+
Alternatively, you can also use the search field in the console, to type a certain tag and filter the flows it's applied to.
48
+
51
49
## Delete a tag from your environment
52
50
53
51
Tags are solution-aware components, so you manage them in your environment's Default solution in the Power Automate portal. Go to the Power Automate portal, select the **Solutions** page, and then select the solution called *Default Solution*. In the list of objects on the left that displays the solution's contents, select the **Tag** component to see all tags available in the current environment (if you have the default *Environment Maker* role with the required permissions).
0 commit comments