cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate III
Advocate III

Http request failed: the timeout was reached

Hi,

 

I have a particular flow which sends out an email everytime a OD4B file is modified. However, intermittently, it's been giving me a timeout error: "Http request failed: the timeout was reached"

 

Do you have any idea how i can solve this ?

 

flow.pngflow 3.png

 

 

8 REPLIES 8
Highlighted
Power Automate
Power Automate

Re: Http request failed: the timeout was reached

Hi,

 

Will you share the id of your flow? When you open the flow for editing, the URL will look like the following:

 

https://flow.microsoft.com/manage/flows/<xxx>

 

Thanks,

 

Dan

 

Highlighted
Regular Visitor

Re: Http request failed: the timeout was reached

Is there a recommended fix for this?  I am having the same issue.

FlowID: 672afca1-c278-4f69-829f-2223b2fc7a46

List ID: c6197dff-ee6e-41e8-9d5f-b0a8d4518fc9

 

The flow criteria is to send an email after Sharpoint list update. 

 

Code

BadRequest
 
Message
Http request failed: the timeout was reached.
Highlighted
Frequent Visitor

Re: Http request failed: the timeout was reached

Getting the same error.

Any success so far?

Highlighted
Advocate I
Advocate I

Re: Http request failed: the timeout was reached

Same problem. Any idea?

 

Thanks

Highlighted
Frequent Visitor

Re: Http request failed: the timeout was reached

Solved !!

My APIs were running at http protocol and Microsoft Flow try to access them by using https. To solve this either run your APIs on https or make changes in swagger.json file to support http scheme by default. If you don't mention any scheme in swagger.json file then by default Microsoft Flow uses https.

Thanks.

Hope it helps !!

Highlighted
Advocate IV
Advocate IV

Re: Http request failed: the timeout was reached

I am also experiencing this issue for the first time today. We are not using any custom APIs, just SharePoint in Office 365 and emails.

 

Error: {
  "error": {
    "code": "BadRequest",
    "message": "Http request failed with status code 'ConnectFailure' and status message: 'Unable to connect to the remote server'."
  }
}

As well as:

 

Error: {
  "error": {
    "code": "BadRequest",
    "message": "Http request failed: the timeout was reached."
  }
}
Highlighted
Frequent Visitor

Re: Http request failed: the timeout was reached

I know the thread's a bit old, but did you find any explanation and/or workaround for this? I'm encountering a similar error in my environment, also without any custom APIs

Highlighted
Advocate IV
Advocate IV

Re: Http request failed: the timeout was reached

@ksteelbaronWe never found a documented root cause for this, but we suspected it was due to too many calls being made under a single account, and that there was no differentiation between the types of calls made programmatically by Flow and the ones made organically by a user checking their email or going in and testing something themselves in the browser.

 

To the best of my recollection, our solution was to create a generic account under which Flows run (e.g. original Owner as well as via Connectors), and around the same time I believe Microsoft announced an increase in the limit of Flow calls per day.

Helpful resources

Announcements
firstImage

Now Live: Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Users online (8,714)