Timeouts running REST -- [ERROR CODE: -1] Read timed out -- after 175 seconds

[Daniel Peel]

I have a rest call that I'm calling via an Action in Flow Designer... that will work... 3 or 4 times in a row then just fail 1 or 2 times... with a timeout at 175+ seconds... it doesn't seem to log any errors in Logs... only in the action outputs... I see some info on community and KBs around SOAP but this isn't soap it's REST. 

The outbound HTTP log shows -- [ERROR CODE: -1] Read timed out -- in the response body

The action shows completed with a running time of 175xxx seconds and an HTTP status code of 0

no other errors in the event log either.. just shows Flow.fire and 175+ seconds but shows processed

Also the interesting thing... is the Endpoint... got the message and processed what was supposed to happen... so I can't tell if it's their system that isn't reporting back or ours that not processing the response correctly... because the endpoint is sync... it will hold the connection until it's processed.

Any ideas? or if more info is needed I can provide it... 

Thanks

[huy le le]

@Daniel Peel 
Do you resolve you problem, please let me know
I have the same issue with you, my the status code always -1 when response time larger than 179 seconds

[Daniel Peel]

Nope, and I can't capture the error, as the error handling in flow doesn't kick in for this.

[Tony Wong]

I experienced a similar issue - REST call (originating from the MID server) timing out after 175000 milliseconds.

Despite it being REST (rather than SOAP) I followed the instructions in KB0547347 and it seems to help - I am no longer seeing timeouts.