Unanswered

HTTP action inside a condition or switch step

(2) Share

Report

Posted on by LK-08041400-0

Hi,

I'm having an issue in Power Automate where I cannot save a flow that contains an HTTP action inside a condition or switch step.

Environment details:
- Custom environment (not default)
- SharePoint "For a selected item" trigger with splitOn
- Power Automate Premium license

The error message is:
"Fehler bei XRM-API-Anforderung: Message: Flow client error returned with status code BadRequest and details InvalidOpenApiFlow. Code: 0x80060467 InnerError:"

What works:
- HTTP actions on the top level (outside conditions) → saves fine
- Conditions with non-HTTP actions inside → saves fine
- Same flow structure works fine in other tools

What doesn't work:
- Any HTTP action inside a condition or switch step → InvalidOpenApiFlow error on save

Things I already tried:
- Rebuilding the flow from scratch
- Using Switch instead of Condition
- Different trigger types
- Checked DLP policies (none exist)
- Checked environment settings

Has anyone seen this before? Is there a setting in the Power Platform Admin Center that controls this?

Thanks!

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

trice602 16,298 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi there!

No there is no admin setting to control this.

Please try putting your http action inside a scope container; this will resolve this for you.

------------------------------------------------

⭐ If this was helpful, please like and check the box below "Does this answer your question" to help others find this too!

Always glad to help! 💯💯💯💯💯

Tom

Follow me on LinkedIn - Thomas Rice, PMP | LinkedIn

Was this reply helpful? Yes No
LK-08041400-0 8 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @trice602, thanks for the suggestion! Unfortunately, wrapping the HTTP actions inside a Scope container did not resolve the issue for me. The error still appears.

Here is my current flow structure:
- SharePoint "For a selected item" trigger
- Get item
- Do Until loop
- Get items (Kundenmapping)
- Initialize variables
- Condition
- True branch: Scope → HTTP POST + HTTP PUT
- False branch: Scope → HTTP POST + HTTP PUT

The HTTP actions are now inside Scope containers within the condition, but I still get InvalidOpenApiFlow on publish. I have attached a screenshot of the current structure.

Any other ideas?

Was this reply helpful? Yes No