Skip to main content

Notifications

Calling Actions from Copilot Studio
Answered

Return value(s) to Power Virtual Agents gives an ActionResponseTimedOut error

Posted on by 85

From time to time, a specific flow that I have gives the following error

 

ActionResponseTimedOut. The execution of template action 'Return_value(s)_to_Power_Virtual_Agents' is failed: the client application timed out waiting for a response from service. This means that workflow took longer to respond than the alloted timeout value. The connection maintained between the client application and service will be closed and client application will get an HTTP status code 504 Gateway Timeout.

 

 

goncaloperes_0-1685453502327.png

 

The settings for the action are as follows:

goncaloperes_1-1685453635435.png

 

If one analyses the flows that gave the error, one thing pops up: an HTTP action.

 

When the flow failed with the error, this HTTP action took ~3min 

goncaloperes_0-1685459967006.png

 

When the error appeared in another flow, HTTP action took ~2min

goncaloperes_1-1685460038549.png

 

This is the HTTP action Settings:

goncaloperes_2-1685460242879.png

 

  • Verified answer
    HenryJammes Profile Picture
    HenryJammes on at
    Re: Return value(s) to Power Virtual Agents gives an ActionResponseTimedOut error

    I think it's by design because waiting over 2 minutes for a bot to respond is a very long time of a chat experience, hence the limitations 

  • goncaloperes Profile Picture
    goncaloperes 85 on at
    Re: Return value(s) to Power Virtual Agents gives an ActionResponseTimedOut error

    Hi @HenryJammes 

    Is there a way to extend that time?
    The problem with the 2min is, for example, when one is interacting with an API that can take more than that.

    It's not that the flow is complex, but that a given action can take longer.

    Sincerely
    G Peres

  • Verified answer
    HenryJammes Profile Picture
    HenryJammes on at
    Re: Return value(s) to Power Virtual Agents gives an ActionResponseTimedOut error

    Hi @goncaloperes,

     

    I believe this is expected, the chatbot has a timeout of 2 minutes when it triggers a Power Automate cloud flow.

    If you have long running logic that doesn't need to return results to PVA, you may add the "Return value to PVA" step before longer actions.

     

    Henry

Helpful resources

Quick Links

Exciting News for Copilot Studio Communi…

Get ready to experience a whole new level of engagement with the Copilot Studio…

Celebrating the May Super User of the…

LaurensM is an exceptional contributor to the Power Platform Community…

Check out the Copilot Studio Cookbook…

We are excited to announce our new Copilot Cookbook Gallery in the Community…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 137,998

#2
RandyHayes Profile Picture

RandyHayes 76,308

#3
Pstork1 Profile Picture

Pstork1 63,059

Leaderboard

Featured topics