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.
Orchestration Powershell Activity timeout: "Terminated the probe because the max timeout was reached: 610 seconds". - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Orchestration Powershell Activity timeout: "Terminated the probe because the max timeout was reached: 610 seconds".
KB0635788

Orchestration Powershell Activity timeout: "Terminated the probe because the max timeout was reached: 610 seconds".


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

Issue

Orchestration Powershell Activity timeout: "Terminated the probe because the max timeout was reached: 610 seconds"



Issue


Some custom Orchestration Powershell Activities take longer to execute. If the response takes more than 610 seconds, the activity will fail and the following error appears in the activity log "Terminated the probe because the max timeout was reached: 610 seconds".

Solution


Increase the probe timeout by adding mid.windows.probe_timeout parameter in the MID Server Configuration Parameters.

  1. Navigate to MID Server > Servers.
  2. From the list of MID Servers, select a MID Server to configure.
  3. Select the Configuration Parameters related list and click New.
  4. Add the mid.windows.probe_timeout, set a value greater than 610, and click Save.
  5. Restart the MID Server.

 


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.