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.
Pattern Debugger Session Timed Out - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Pattern Debugger Session Timed Out
KB0854603

Pattern Debugger Session Timed Out


1940 Views Last updated : Jan 28, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Pattern Debugger error:

Session timed out.

Release

All supported releases.

Cause

The pattern designer needs to collect all dependent data before a step can run. For example, pattern "Tomcat" and "Tomcat WAR" must be executed before running any step from a connection section for "Tomcat WAR" pattern. Some steps, or a collection of steps, can take longer to run than the default Pattern Debugger session max time out value. If that value is passed, the “Session timed out” error is thrown.

Note: Ecc queue records of topic PatternDebuggerProbe will be created when the pattern debugger is being used. Subtract the created timestamp, of the output record, from the processed timestamp, of the input record, to determine how long it took to collect the necessary dependent data.

Resolution

Increase Max Time Out

Set following property to a value greater than it took the PatternDebuggerProbe to collect the necessary data:

sa.debugger.max_timeout

Review MID Server Logs

Review the MID server logs to determine what step, or collection of steps, pushed the debug session to the max time out. Troublesome step could be temporarily disabled while debugging or working on a pattern.

Related Links

  • Properties installed with service mapping

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.