Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to trace certain activities and service files



Unable to trace certain activities and service files. When the tracer starts, an error pops up stating that the activity is already being traced by the operator ID 'op1' from another requestor. However, this requestor is not present in the Requester management.

Error Messages

The rule is already being traced by operator 'op1' in another requestor session.

Steps to Reproduce

  1. Open a Service SOAP rule
  2. Click Actions > Trace. The tracer launches and the error displays


  1. Apply HFix-40458 and HFix-41101
  2. Clear the stale tracer session in the environment from the Listener page


Published July 23, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us