Skip to content

Commit 5b9a8b3

Browse files
authored
Update triggers-troubleshoot.md
1 parent 5583e33 commit 5b9a8b3

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

support/power-platform/power-automate/flow-run-issues/triggers-troubleshoot.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -357,4 +357,10 @@ Admins can use the [Microsoft.PowerApps.Administration.PowerShell](https://www.p
357357
Get-AdminFlowWithMigratingTriggerUrl -EnvironmentName <EnvironmentName>
358358
```
359359

360-
The cmdlet outputs the `DisplayName` and `FlowName` (ID) of each flow whose trigger URL will be migrated.
360+
The cmdlet outputs the `DisplayName` and `FlowName` (ID) of each flow whose trigger URL will be migrated.
361+
362+
Note: For smoother retrieval of all impacted flows at tenant level, You can use Get-AdminPowerAppEnvironment [script](https://learn.microsoft.com/en-us/powershell/module/microsoft.powerapps.administration.powershell/get-adminpowerappenvironment?view=pa-ps-latest) to list all environments in a tenant and subsequently use the Get-AdminFlowWithMigratingTriggerUrl to list impacted flows in the environment.
363+
364+
```
365+
Get-AdminPowerAppEnvironment
366+
```

0 commit comments

Comments
 (0)