Answered

HTTP Trigger Issues

(0) Share

Report

Posted on by BradK

Good morning all,

First, let me say that I am aware of the upcoming changes to the HTTP URLs and while I believe this issue is related, it's not due to a lack of trying on my part.

I am wondering if anyone else has observed the following:

The 'old' HTTP URLs, which were stated to work until November 30th, stopped working in at least one environment of ours sometime between November 7-10. Now they return a 401 error with the message "DirectApiRequestHasMoreThanOneAuthorization" even if zero auth methods are provided in the request.
Because of this, we fast-tracked deploying the new URLs to our assets and tested successfully overnight - I would like to reiterate that we were calling the new URLs 6 hours ago and they worked as expected.
As of this morning, the 'new' HTTP URLs also are not working in that same environment, the request seems to get received by the trigger but it doesn't process it in any way or execute subsequent steps in the flow. The flow will hang in 'running' status with only the trigger action executed but nothing subsequently. After about 2 minutes the calling application will throw a 504, but the flow will stay alive until cancelled.

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Suggested answer

venturemavenwill 1,198 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

This is a known issue...unfortunately Microsoft seems to be performing updates, and they have updated the keys used to authenticate the endpoint several times already, resulting in different URL

You should have received several emails telling you that the trigger URL has been updated, but try to grab the trigger URL again and replace it with the current one.

1 people found this reply helpful.

Was this reply helpful? Yes No
BradK 26 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the reply @venturemavenwill. I actually tried that as part of troubleshooting before posting (directly visited the flow and copied the trigger URL) to no avail. I probably should have included that detail in the original post, whoops.

Worth noting that I also created a brand-new flow with just an HTTP request trigger and a response - that one also does not work in the environment that we observed the issue in, but it does work in a sandbox environment that I made it in to double-check. So I think this is some sort of environment-specific issue and will open a ticket with MS.

Was this reply helpful? Yes No
Suggested answer

venturemavenwill 1,198 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Interesting. Can you check if Administration Mode is on in the environment?

In case you haven't seen it, it's in the Power Platform Admin Center, in your Environment. Click "Edit" on Details

If this is enabled, disable it.

1 people found this reply helpful.

Was this reply helpful? Yes No
BradK 26 on at

Like (0)

Report
Copy link

Link copied!

Just checked, administration mode is not enabled on that environment.

Thanks for sharing the path to it, that was not where I would have looked for that setting on my own.

Was this reply helpful? Yes No
Verified answer

BradK 26 on at

Like (0)

Report
Copy link

Link copied!

Just to post for clarity, I think my issues are related to Service Health Issue FL1184861 which is actually affecting all cloud flows in this one environment, not just HTTP ones. It just turned out that we happened to be trying to deploy changes to the HTTP flows at exactly the time as the issues began (8am EST), lucky us!

Going to mark as resolved for now since I think this wasn't a 'me' problem after all.

Was this reply helpful? Yes No