The Wayback Machine - https://web.archive.org/web/20241005070726/https://learn.microsoft.com/en-us/answers/questions/1188979/how-to-avoid-action-response-time-out
I use the response action after creating a file to the specific file server and I've faced an error with the massage: "ActionResponseTimedOut. The execution of template action 'Response' 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."
Is there any ways I could avoid this error?
I use "file system" connector to create a file to the specific file server and I faced an error with status code 429 so that I changed the retry policy on my connector action. I have no longer faced the 429 error, but now I've faced this timeout error.
@開発者 アカウント Thanks for reaching out. If you are getting "504 Gateway Timeout" in your logic app, it means that the server is taking too long to respond to the request. This error can occur due to various reasons such as:
The server is taking too long to process the request.
The server is down or not responding.
The network connection is slow or unstable.
Are you using OPDG to connect to your on primes file system or directly connecting to your file system without OPDG. Is there limitation on the number of connectors to your file system server and have you verified file system logs and whether your file server was under high utilization? Timeout value cannot be increased for the consumption logic app but if you have standard logic app then the timeout value may be increased depending upon if you are using in build connector and the configuration supports it.
@MayankBargali-MSFT
Thanks for your advice. I have tried to increase the timeout value, but I still face the same issue.
Is there any way I can bulk retry the failed action? Do I need to retry them one by one?
