Unanswered

Http request failed: the timeout was reached

(1) Share

Report

Posted on by PriscillaHM

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 3.png

Categories:

Using flows

I have the same question (0)

All responses (8)

Answers (0)

dkappes on at

Like (0)

Report

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

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

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.

Was this reply helpful? Yes No
Lipsy 16 on at

Like (0)

Report

Getting the same error.
Any success so far?

Was this reply helpful? Yes No
uvera 4 on at

Like (0)

Report

Same problem. Any idea?

Thanks

Was this reply helpful? Yes No
Lipsy 16 on at

Like (0)

Report

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 !!

Was this reply helpful? Yes No
Tanner 190 on at

Like (0)

Report
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." } }

Was this reply helpful? Yes No
ksteelbaron 6 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Tanner 190 on at

Like (0)

Report

@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.

Was this reply helpful? Yes No