How can I avoid the "No response for ECC message request with sysid=xxx after waiting for 30 seconds

[Aishwarya NG]

Hello ServiceNow Community,

We are currently running San Diego.

and I have the following section of code in a Registration workflow

var request = new sn_ws.RESTMessageV2();
request.setHttpTimeout(360000000);

request.setEccParameter('skip_sensor', true);
request.setEndpoint(_endPoint);
request.setHttpMethod('post');
if (payload) {
payload = this.ESCAPE_CHARACTER(payload);
request.setRequestBody(payload);
}
request.setMIDServer(this.midServer);
request.setRequestHeader('Accept', 'application/json');
request.setRequestHeader('Content-Type', 'application/json');
request.setRequestHeader('Authorization', authorizationString);

var response = request.executeAsync();
response.waitForResponse(360);

In addition to the response.waitForResponse(360); line above, I have also added the System Property glide.rest.outbound.ecc_response.timeout with an integer value of 360 and added glide.http.outbound.max_timeout.enabled with a value false.  

But I am still receiving the error "No response for ECC message request with sysid=xxx after waiting for 30 seconds in ECC Queue".

Any idea why this REST API call is still timing out after only 30 seconds (instead of the 6 minutes I would expect based on the above settings)?

[Tony Chatfield1]

Hi, setEccTopic() may offer a solution.

Outbound REST Web Services RESTMessageV2 and SOAPMessageV2 execute() vs executeAsync() Best Practice...

The article also covers why extended response times are very very BAD.

Personally, I would escalate the target platform as a business risk.