Showing results for 
Search instead for 
Did you mean: 
Resolver I
Resolver I

The execution of template action <> is skipped: another response action has already executed



The flow is triggered by incoming POST request and has multiple conditions and switches.

Inside one of the paths there are two HTTP actions: first one is HTTP GET followed by HTTP Response and more steps, then another HTTP (POST) followed by HTTP Response step.

Two Response steps have different Status codes, both set to run asynchroniously and both configured to run after success of the previous step.


But the second Response action fails with the message

The execution of template action '<HTTP POST action name>' is skipped: another response action has already executed.


Is there a limit on the number of Response actions within a flow? And if so, how do I work around this limit?


Background: first HTTP request is to query a system for existence of an item and the second one is to create one if not found. In both cases responce is a large JSON so I'm using response action to get it and pass to "pass json" action to extract a specific value from the system response.


Thank you.

Resolver I
Resolver I

Not answering the question, but I just realized I did not need the second Response action at all because Parse JSON worked perfectly with the "Body" returned from the HTTP POST action.

I'm still interested in finding about the Response action though.

Helpful resources

UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Top Solution Authors
Users online (3,693)