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.
The settings for the action are as follows:
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
When the error appeared in another flow, HTTP action took ~2min
This is the HTTP action Settings:
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
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
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