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.
Resolving the task timeout problem - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Resolving the task timeout problem
KB0623495

Resolving the task timeout problem


4140 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Resolving the task timeout problem



Symptoms


There are task timeout error messages on the map and on the Discovery Messages tab.

Possible Causes/Resolutions


There are several possible causes and resolutions.

Possible Cause/Resolution 1

Cause – The MID Server does not pick up tasks because it does not pull messages from the ECC queue on time. 

Resolution – Perform the following steps:

  1. Navigate to the ECC\Queue.
  2. Query for records with Topic ServiceDiscoveryProbe, Source matching the IP address on the message, and State is not Processed.
  3. Check that there are Queue records classified as Output, with the State attribute set to Ready. 
  4. Check the CPU consumption on the MID and if the MID CPU consumption is high, add MID Servers using the same range on another machine in order to reduce the load. 

Possible Cause/Resolution 2

Cause – The MID Server does not pick up tasks because it stopped communicating with the ServiceNow instance.

Resolution – Restart the MID Server.

Possible Cause/Resolution 3

Cause – The ServiceDiscoveryProbe probe working on the MID Server is slow or stopped functioning. The relevant MID Server is busy with a task that is taking a long time. 

Resolution – Perform the following steps:

  1. Navigate to the ECC\Queue.
  2. Query for records with Topic ServiceDiscoveryProbe, Source matching the IP address on the message, and State is not Processed.
  3. Check that there are Queue records classified as Output with the State set to Processing.
  4. Change the mid.log.level MID configuration parameter to debug, and download the MID Sever logs.
  5. Look for exceptions that can help understand why pattern execution is hanging. Modify the task that takes a long time to run for efficiency.

Possible Cause/Resolution 4

Cause – The instance is highly loaded and cannot process all input requests on the ECC queue in time. The Worker threads do not initiate Service Discovery Sensors that must pick up the input record from the ServiceDiscoveryProbe.

Resolution – Perform the following steps:

  1. Navigate to the ECC\Queue.
  2. Query for records with Topic ServiceDiscoveryProbe, Source matching the IP address on the message, and State is not Processed.
  3. Check that there are Queue records classified as Input.
  4. Isolate the flows that mostly occupy the instance by navigating to Active Transactions or Slow Transactions.

    For more information, see the product documentation topic View and kill active transactions.

Possible Cause/Resolution 5

Cause – The processing of the ServiceDiscoveryProbe failed.

Resolution – Perform the following steps:

  1. Navigate to the ECC\Queue.
  2. Query for records with Topic ServiceDiscoveryProbe, Source matching the IP address on the message, and State is not Processed.
  3. Check that there are Queue records classified as Input and the State is set to Error.
  4. In the instance logs, search for ServiceWatchInitialDiscoveryResultHandler.
  5. Find the log message that indicates the reason for this sensor failure and fix it.

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.