Applies to Product - Power Apps
What’s happening?
Customers are experiencing connection errors when running flows in Power Apps that interact with Azure Automation. The errors include:
Next Steps
If the issue persists:
What’s happening?
Customers are experiencing connection errors when running flows in Power Apps that interact with Azure Automation. The errors include:
- "BadGateway" responses
- Timeouts after two minutes
- Access permission issues related to Azure subscriptions
Reason:
- Flow Metadata Mismatch: The flow may have been updated to use a new connection, while the app still references outdated metadata. This mismatch can cause execution failures.
- Access Configuration: Users may lack the necessary permissions to execute Azure Automation jobs, or the Azure service connections may not be properly established.
Resolution:
For "BadGateway" and Timeout Errors:
- Open the app in the latest version of Power Apps Studio.
- Navigate to the Data sources pane.
- Remove all associated flows from the app.
- Re-add the flows to ensure the latest metadata is referenced.
- Save and republish the app.
- Confirm that users have the correct roles and access rights to the Azure Automation resources.
- Verify that the Azure connections are valid and active.
- Ensure the users have access to the relevant Azure subscriptions.
Next Steps
If the issue persists:
- Check the connection status in Power Apps and Power Automate.
- Review flow configurations and gateway setup.
- Consult the https://admin.powerplatform.microsoft.com for diagnostics and logs.
- Guide to cloud flow sharing and permissions – Power Automate
- Manage shared flows with users outside an environment
