Skip to content

Fixed typo #1853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fixed typo #1853

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ab6f308
Fixed typo
BCBuizer Apr 13, 2025
19d663b
minor updates
lucciz01 Apr 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions ...rt/power-platform/power-apps/connections/best-practices-when-updating-a-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Error codes on Flow run
description: Describes best practices and steps to mitigate common errors when running Microsoft flows in Power Apps.
ms.reviewer: mlalavat
ms.date: 03/01/2024
ms.date: 04/15/2025
ms.custom: sap:Connections\Creating or updating connections
---
# Best practices when updating a flow used by a Power App
Expand Down Expand Up @@ -173,7 +173,7 @@ The reason is that there might be a change to the flow in the target environment
> [!NOTE]
> There can be no unmanaged layers on either the flow or the app because this can cause issues in connection to the flow.

## Error code "NotAllowedConnectionReferenceon" on Flow run
## Error code "NotAllowedConnectionReference" on Flow run

```output
{
Expand All @@ -197,6 +197,8 @@ This error means that the app has flow metadata that specifies that a SQL connec

#### Mitigation option 1

Reset the flows in the app:

1. In the source environment, edit the app. Remove and then re-add the flows to the app. Save and publish the changes.
2. In the target environment, remove all unmanaged layers on the app and flow.
3. Export the solution and import it into the target environment.
Expand All @@ -206,12 +208,12 @@ This error means that the app has flow metadata that specifies that a SQL connec

#### Mitigation option 2

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

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

## Other symptoms

Expand Down