Others

How to Fix Power Automate Cloud Flow Registration Failed with Custom Connectors

Maira MehtabMaira Mehtab Oct 26, 2026 868 views

Question details

Users experience a 'Failed during HTTP send request' error when trying to register a Power Automate cloud flow connected to a Power Apps canvas app using custom connectors.

How to Fix Power Automate Cloud Flow Registration Failed with Custom Connectors
Product
Microsoft Power Automate
Device & OS
not provided
Scenario
Registering a cloud flow with a Power Apps canvas app using run-only user connections.
Observed behavior
The flow registration fails with a 'Failed during HTTP send request' error across multiple environments.
Before you start

Ensure you have administrator or owner permissions for both the Power Automate cloud flow and the associated Power Apps canvas app before modifying connection references.

Solution 1Recommended

Verify Connector Permissions and Run-Only User Settings

Check and adjust the permissions and connection ownership settings to ensure run-only users have the correct access to the custom connector.

The 'Failed during HTTP send request' error often occurs because the account running the flow lacks the necessary permissions to authenticate against the custom connector. Adjusting the run-only permissions ensures the correct connection reference is utilized during execution.

1
Open flow settings

Navigate to the Power Automate portal and open the details page for the affected cloud flow.

2
Edit run-only users

Locate the 'Run-only users' section in the bottom right corner of the flow details page and click 'Edit'.

3
Configure connection preferences

Verify that the connections for the custom connector are set correctly. Choose either 'Provided by run-only user' if users should authenticate themselves, or select a specific authorized connection.

4
Verify connector sharing

Check the custom connector's sharing settings in the Data section to ensure the runtime users have been granted explicit permissions to use it.

5
Test the flow

Save the flow configuration and test the registration again directly from the Power Apps canvas app.

Verify Connector Permissions and Run-Only User Settings
Environment Configuration: Since this issue spans multiple environments, ensure that the custom connector is correctly imported, updated, and authenticated in the target environment.
Free Microsoft Office alternative

Looking for a Reliable and Lightweight Office Suite?

While troubleshooting Microsoft Power Automate and Power Apps, consider optimizing your daily document workflows with WPS Office. It provides a lightweight, highly compatible alternative to Microsoft Office, ensuring seamless transitions without the heavy subscription costs.

  1. 1. Download WPS Office: Visit the official WPS website to download the free installation package.
  2. 2. Install the application: Run the installer and follow the on-screen instructions to set up WPS Office on your computer.
  3. 3. Open your files: Launch WPS Office and instantly open your existing Microsoft Word, Excel, or PowerPoint documents without losing formatting.
Fully compatible with Microsoft Excel, Word, and PowerPoint formats.Lightweight design ensuring fast installation and smooth operation on any device.Familiar, easy-to-use interface that requires no learning curve.Built-in PDF editing and cloud collaboration tools.
microsoft office alternative - wps office

Frequently Asked Questions

What causes the 'Failed during HTTP send request' error in Power Automate?

This error usually occurs when there are permission mismatches in connection references, incorrect run-only user settings, or network issues preventing the custom connector from reaching its endpoint API.

How do I fix connection reference errors across different environments?

When migrating flows across environments using solutions, you must recreate or re-authenticate connection references in the target environment to ensure the flow connects securely to local resources.

Can run-only users authenticate custom connectors automatically?

Run-only users can authenticate custom connectors if the flow is configured to prompt them for their own credentials upon execution, or if the flow maker has explicitly embedded a shared connection with appropriate access rights.

Why does my canvas app fail to trigger the cloud flow?

The canvas app might fail to trigger the flow if the flow's input parameters were recently changed without refreshing the flow connection inside the Power Apps studio, leading to a schema mismatch.