Power Automate allows PowerApps to trigger flows using the PowerApps (V1 & V2) trigger. However, you may encounter issues where the flow does not start when triggered from PowerApps.
Common Error Message:
“PowerApps trigger is not working – Issues with the PowerApps trigger not being invoked correctly.”
This issue prevents the flow from executing as expected, leading to failures in automation processes.
2. Causes of “PowerApps Trigger Not Working”
Several factors can prevent the PowerApps trigger from working:
- Incorrect Trigger Type Used – Using an outdated or incorrect PowerApps trigger in the flow.
- Flow Not Properly Connected to PowerApps – The flow must be explicitly linked to a button or action in PowerApps.
- Missing or Incorrect Parameters – If required input parameters are missing, the flow may not execute.
- Authentication or Permission Issues – The user running the app may lack permission to execute the flow.
- Power Automate Service Outage – Temporary Microsoft service outages can prevent trigger execution.
- Flow Disabled or Turned Off – If the flow is disabled, the trigger cannot execute.
- Delegation and Data Source Issues – Some triggers fail due to delegation limits or connection errors.
- PowerApps and Flow Running in Different Environments – If the PowerApps app and the flow are in different environments, the trigger may not work.
- Error Handling Not Implemented – Flows without error handling may fail silently.
- API Throttling or Execution Limits – Power Automate limits the number of runs per minute/hour based on licensing.
3. Step-by-Step Troubleshooting Guide
Step 1: Verify That the Correct PowerApps Trigger Is Used
Power Automate offers two PowerApps triggers:
“PowerApps (V2)” – Recommended
- Allows named input parameters.
- Provides better stability and debugging options.
“PowerApps (V1)” – Deprecated
- Does not support named parameters.
- Can cause unexpected failures.
✔ Solution:
- If using PowerApps (V1), switch to PowerApps (V2).
- Edit the flow, remove the V1 trigger, and add PowerApps (V2).
Step 2: Ensure the Flow Is Connected to PowerApps
- Open PowerApps (https://make.powerapps.com).
- Select the app that should trigger the flow.
- Open the button or control that calls the flow.
- Click Actions > Power Automate > Add Flow.
- Select the correct flow from the list.
- Save and publish the app.
Example of a Correct Connection in PowerApps Formula:
Set(response, 'MyFlow'.Run("Parameter1", "Parameter2"))
Example of an Incorrect Connection (Missing Parameters):
'MyFlow'.Run()
Solution:
- Ensure that all required parameters are passed when calling the flow.
Step 3: Check Flow Run History for Errors
- Open Power Automate (https://flow.microsoft.com).
- Navigate to My Flows and locate the affected flow.
- Click Run History to review past executions.
- If the flow did not run, the trigger did not fire.
- Click on any failed runs to view detailed error messages.
Example of a Successful Trigger Execution:
Trigger: PowerApps
Status: Succeeded
Example of a Failed Trigger Execution:
Trigger: PowerApps
Status: Failed (Invalid Parameters)
Solution:
- Fix missing or incorrect parameters in the PowerApps formula.
Step 4: Ensure That PowerApps and Flow Are in the Same Environment
- Open Power Automate and check the flow’s environment.
- Open PowerApps and check the app’s environment.
- If the environments do not match, the flow will not be triggered.
Solution:
- Move the flow to the same environment as the PowerApps app.
Correct Example:
PowerApps Environment: "Default"
Power Automate Flow Environment: "Default"
✔ Works correctly
Incorrect Example:
PowerApps Environment: "Production"
Power Automate Flow Environment: "Sandbox"
❌ Trigger will not work
Step 5: Check User Permissions and Authentication Issues
- The user triggering the flow must have Execute Permissions on the flow.
- If using shared PowerApps, ensure that all users have access to the connected services (SharePoint, Dataverse, etc.).
Solution:
- Open Power Automate > My Flows.
- Click on the flow name and go to Manage Run-Only Users.
- Add any missing users who need to trigger the flow.
- If authentication is required, reconnect the PowerApps connection in Power Automate.
Step 6: Check If the Flow Is Disabled or Has Hit Its Run Limit
- Open Power Automate > My Flows.
- Ensure the flow is turned ON.
- If your Power Automate plan has execution limits, check if the flow has been throttled.
Solution:
- If the flow was disabled due to API limits, upgrade to a higher Power Automate plan.
- Reduce flow execution frequency by adding Delays in PowerApps before calling the flow.
Step 7: Test the Flow Manually from Power Automate
- Open Power Automate > My Flows.
- Select the PowerApps-triggered flow.
- Click Test > Manually Trigger.
- Enter sample input parameters.
- Click Run Flow and check if it executes correctly.
Solution:
- If the flow runs successfully manually, the issue lies in PowerApps integration.
- If the flow fails manually, check the error message for specific issues.
Step 8: Add Error Handling to Prevent Silent Failures
- Use “Scope” actions in Power Automate to catch errors and display messages in PowerApps.
Example of an Error Handling Setup in PowerApps:
Set(response, 'MyFlow'.Run("Parameter1", "Parameter2"));
If(IsError(response), Notify("Flow failed. Please try again.", NotificationType.Error))
Solution:
- This prevents silent failures and helps users see what went wrong.
4. Preventative Measures
To prevent PowerApps trigger issues in the future:
✔ Use PowerApps (V2) triggers instead of PowerApps (V1).
✔ Ensure PowerApps and Flow are in the same environment.
✔ Pass correct parameters when calling the flow.
✔ Give all users necessary run permissions.
✔ Monitor Power Automate run history for failures.
✔ Check Power Automate plan limits to prevent throttling.
✔ Use error handling in PowerApps to show failure messages.