Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Outbound REST or SOAP messages timeout after upgrade - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Outbound REST or SOAP messages timeout after upgrade
KB0748136

Outbound REST or SOAP messages timeout after upgrade


4419 Views Last updated : Dec 21, 2023 public Copy Permalink
KB Summary by Now Assist

Issue

Experiencing REST API timeouts after a recent upgrade? This article provides helpful troubleshooting information and steps to resolve the issue.

Symptoms

After upgrading to Madrid, Kingston Patch 14 or higher, or London Patch or higher, outbound API messaging, RESTMessageV2 and SOAPMessageV2 API calls, may start to time out after 30 seconds for a response. But before the upgrade the timeouts did not occur.

You might see errors such as this in the logs:

Error: No response for ECC message request with sysid=nnnn... after waiting for 30 seconds in ECC Queue

Release

  • Madrid
  • London Patch 7 (or higher)
  • Kingston Patch 14 (or higher)

Cause

In Madrid, London Patch 7+, and Kingston Patch 14+, two system properties were added on the backend:
glide.http.outbound.max_timeout with a maximum value of 30 seconds
glide.http.outbound.max_timeout.enabled with a default value of true

The property glide.http.outbound.max_timeout specifies the number of seconds that RESTMessageV2 and SOAPMessageV2 APIs wait for a response from a synchronous call, and the default and maximum value for this property is 30 seconds. As a result, outbound REST and SOAP API calls will start to time out after waiting 30 seconds for a response.

Resolution

To resolve this issue, perform both of the following:

  1. Add the following system property on the UI:
    Name: glide.http.outbound.max_timeout.enabled
    Type: boolean
    Value: false
  2. Use the waitForResponse() method to set the timeout in the REST or SOAP messages.
    Here are some examples:
    Asynchronous RESTMessageV2 example
    Asynchronous SOAPMessageV2 example

Related Links

The properties glide.http.outbound.max_timeout and glide.http.outbound.max_timeout.enabled may not be documented in the Kingston and London documentation since they were added to these releases in later patches.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.