Http request action sometimes failed due to "The server did not respond within the timeout limit."

Like (0) Share

Report

Posted on 16 Nov 2024 09:35:04 by johnjohnPter

1,546 Super User 2024 Season 1

I have a Send Http request to external system premium action, which get the calls done by our call center in the current Date (such as on 14 November or on 15 November, etc..), but sometimes on specific days where we have many calls, the action failed due to timeout :-

{
"error": {
"code": "BadRequest",
"message": "Http request failed: the server did not respond within the timeout limit. Please see logic app limits at https://aka.ms/logic-apps-limits-and-config#http-limits."
}
}

For example yesterday the flow completely failed to get the data after 12 retries:-

While 2 days ago, it was able to get the data from the external API after 4 retries:-

one the weekends it gets the data directly without any retries...

So my question is how i can increase the time the action will be waiting for the response from the external API? now when i use some API tools to pull the XML from the API such as postman, i can see that the API takes couple of minutes to response, espically when there are lot of data for that day, but it will return the result... so how i can improve the wait time for the HTTP action???, here is the settings for the action:-

All responses (3)

Answers (0)

Pstork1 66,277 Most Valuable Professional on 16 Nov 2024 at 23:36:41

Like (0)

Report

Http request action sometimes failed due to "The server did not respond within the timeout limit."

The point is that the default pattern has a fairly quick retry rate. The exponential pattern waits longer between each retry and the fixed interval lets you set a longer wait between retries. The number of retries is fixed, but you can increase the wait time between and the overall time it will wait for the extended retry timing. The only other thing you can do is improve the HTTP server that you are calling so you don't have to retry as much. Its doing that because its too busy and the request is too big.
johnjohnPter 1,546 Super User 2024 Season 1 on 16 Nov 2024 at 21:20:36

Like (0)

Report

Http request action sometimes failed due to "The server did not respond within the timeout limit."

@Pstork1

I checked the post but it is saying how to define the number of retries ., which is not a problem in my case , my main issue, is how to improve the wait time before raising a timeout, i tried this setting, to define the Duration to be 10 minutes:-

but did not have any change,, still a timeout will be raised if we have large number of items,from the API
Suggested answer

Pstork1 66,277 Most Valuable Professional on 16 Nov 2024 at 16:25:36

Like (0)

Report

Http request action sometimes failed due to "The server did not respond within the timeout limit."

Change the overall timeout setting for the action and change the Retry Policy to Fixed Interval. this article explains how to do it.

Setting Retry Policy for an HTTP request in a Flow | Power Automate - D365 Demystified

Community site session details

Http request action sometimes failed due to "The server did not respond within the timeout limit."

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Congratulations to the April Top 10 Community Stars!

Leaderboard > Power Automate - Building Flows

Featured topics

Product updates

Community site session details

Http request action sometimes failed due to "The server did not respond within the timeout limit."

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Congratulations to the April Top 10 Community Stars!

Subscribe to this forum!

Select categories

Leaderboard > Power Automate - Building Flows

Featured topics

Product updates