REST or SOAP outbound message through MID Server times out after 30 seconds in ECC QueueIssue When an asynchronous outbound REST or SOAP message runs through a MID Server, the following error is thrown if the response takes longer than 30 seconds. The error occurs even when a different timeout is set with the waitForResponse() method in the script. No response for ECC message request with sysid=*** after waiting for 30 seconds in ECC Queue Release All supported versions Cause The 30 second limit applies to outbound requests through the MID Server unless the timeout property is turned off. The following system properties control this behavior: •glide.http.outbound.max_timeout •glide.http.outbound.max_timeout.enabled You can find the latest documentation on these properties here: https://www.servicenow.com/docs/r/api-reference/web-services/r_HTTPConnectionManagementProps.html Resolution To define a timeout longer than 30 seconds, complete the following steps: 1.Set the glide.http.outbound.max_timeout.enabled system property to false. 2.Use the waitForResponse() method in the script to set the timeout. For script samples, see the following examples in Related Links: •Scripted REST API example script samples •Asynchronous SOAPMessageV2 example NOTE: If glide.http.outbound.max_timeout.enabled is set to true and a value is passed in the waitForResponse() method, the system uses the smaller value from either the waitForResponse() method or the glide.http.outbound.max_timeout system property. Related Links •View Scripted REST API example script samples •View Asynchronous SOAPMessageV2 example script •View available system properties documentation •Review outbound REST web service documentation •Review outbound SOAP web service documentation •Review general guidelines for RESTMessageV2 and SOAPMessageV2 https://www.servicenow.com/docs/r/api-reference/web-services/r_HTTPConnectionManagementProps.html