HTTP Action Connection Not Found

(0) Share

Report

Posted on by coopermeister

Since 11 September at 08:25, I’ve been receiving an error when using the HTTP action in Power Automate. All flows prior to this had been running for months without issue. I haven’t changed any flows in Production and no DLP policies have been modified.

The request is very simple: the HTTP action uses No authentication and posts a small body to obtain a token. When I run the same call with curl from the terminal, the host returns a valid response, so this points to an issue within the Power Automate HTTP action rather than the endpoint.

The error message I am getting informs me:

“The request has SAS authentication scheme, 'MSAuth1.0' authorization scheme or internal token scheme. Only one scheme should be used.”

I’m also seeing an error stating that a connection cannot be found. However, the HTTP action is configured with No authentication and doesn’t have a connection I can assign.

I’m unable to debug this any further from my side so any help would be appreciated.

Categories:

Connector development

I have the same question (0)

All responses (6)

Answers (0)

Tomac 4,048 Moderator on at

Like (1)

Report
Copy link

Link copied!

An HTTP 400 code is returned by the remote server, not by Power Automate. Have you checked with the admin of the server you're reaching out to and asked if any changes have been made?

Was this reply helpful? Yes No
coopermeister 10 on at

Like (0)

Report
Copy link

Link copied!

Good point. This endpoint isn’t managed by us, so I’ll check with the admin team who host it. I only thought it might be a Power Automate issue because we use this endpoint for several applications that sit outside of Power Apps, and only the Power Automate flow is failing. This error message flagged it as something related to Power Automate:

“The request has SAS authentication scheme, 'MSAuth1.0' authorization scheme or internal token scheme. Only one scheme should be used.”

I’ll do some more digging. Thank you for your help.

Was this reply helpful? Yes No
Suggested answer

CFernandes 8,482 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hey @coopermeister What you’re seeing, "message": "errorCode.connectionNotFound with Status code 400 means the Power Automate connector couldn’t find/resolve the connection it needs. The call probably never reached the remote server; the platform rejected it first, returning a 400.

Can you open Connection references to confirm the action is bound to a valid connection (re-bind if you recently imported the flow), then in the flow designer re-auth the connection by re-selecting or re-creating it (look for the “Fix connection” banner).

If that still doesn’t work, test the endpoint in Postman to see whether the request succeeds or returns an error, capture the exact status code and response body for comparison.

If it helped you, please click "Does this answer your question?" and give it a like or mark it as Solution, it helps others in the community find answers more easily!
Connect With Me:
💼 LinkedIn: Clavin Fernandes
📺 YouTube: Clavin Fernandes
📝 Blog: clavinfernandes.wordpress.com
🌐 Community Website: PPUG.org
👥 Join our Community: Power Platform User Group

Was this reply helpful? Yes No
coopermeister 10 on at

Like (0)

Report
Copy link

Link copied!

The HTTP action in Power Automate doesn’t have a connection you can associate with it, unless it’s hidden somewhere I can’t see. All the connections are in a valid state as part of the solution. I’m also using an HTTP action in a different flow within another solution, and that one isn’t failing.

I can make a cURL request from the terminal to this endpoint without any issues, and we also have other connections to the same endpoint that aren’t failing.

I have a feeling this is part of an ongoing bug that started on the same day. Although it’s a different error message and relates to authentication, it began around the same time and involves the same HTTP action.

https://admin.powerplatform.microsoft.com/support/knownissues/5625835

Was this reply helpful? Yes No
CFernandes 8,482 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@coopermeister - That makes a lot of sense. I’d suggest opening a support ticket if you’d like to get to the bottom of it as we have checked all the configurations and also the CURL request works.

If it helped you, please click "Does this answer your question?" and give it a like or mark it as Solution, it helps others in the community find answers more easily!
Connect With Me:
💼 LinkedIn: Clavin Fernandes
📺 YouTube: Clavin Fernandes
📝 Blog: clavinfernandes.wordpress.com
🌐 Community Website: PPUG.org
👥 Join our Community: Power Platform User Group

Was this reply helpful? Yes No
coopermeister 10 on at

Like (1)

Report
Copy link

Link copied!

I raised a support ticket last week but seemed to hit a wall with poor information and little interest in helping to resolve it.

Interestingly, when I checked the flows this morning, they were working again and no longer failing. I haven’t changed anything, so I’m not sure how it resolved itself. Anyway, I guess it was just one of those things.

Was this reply helpful? Yes No