Skip to content

Commit 19d663b

Browse files
authored
minor updates
1 parent ab6f308 commit 19d663b

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

support/power-platform/power-apps/connections/best-practices-when-updating-a-flow.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Error codes on Flow run
33
description: Describes best practices and steps to mitigate common errors when running Microsoft flows in Power Apps.
44
ms.reviewer: mlalavat
5-
ms.date: 03/01/2024
5+
ms.date: 04/15/2025
66
ms.custom: sap:Connections\Creating or updating connections
77
---
88
# Best practices when updating a flow used by a Power App
@@ -196,7 +196,8 @@ This error means that the app has flow metadata that specifies that a SQL connec
196196
> Make sure to perform the following steps in the source or development environment and update the solution. Once the solution is updated, import it to all the target or production environments.
197197
198198
#### Mitigation option 1
199-
Resetting the flows in the app:
199+
200+
Reset the flows in the app:
200201

201202
1. In the source environment, edit the app. Remove and then re-add the flows to the app. Save and publish the changes.
202203
2. In the target environment, remove all unmanaged layers on the app and flow.
@@ -206,13 +207,13 @@ Resetting the flows in the app:
206207
> There can be no unmanaged layers on either the flow or the app because this can cause issues in connection to the flow.
207208
208209
#### Mitigation option 2
210+
209211
Change the connection from **Embedded** to **Invoker**:
210212

211213
1. Navigate to the flow portal to edit and update the flow settings.
212214
2. On the flow details page, in the **Run only users** section, select **Edit**.
213215
3. To update the flow connection source to **Invoker**, select **Provided by run-only user** and save.
214-
4. To update the flow connection source to **Embedded**, select **Use this connection** and save.
215-
5. Verify by triggering the flow. You see that the "install flow network" calls now are succeeding.
216+
4. Verify by triggering the flow. You see that the "install flow network" calls now are succeeding.
216217

217218
## Other symptoms
218219

0 commit comments

Comments
 (0)