Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Duplicate trace error

Updated on April 5, 2022

If the node hosting your trace session fails and you attempt to trace the same service again, you might encounter a duplicate trace error. Clear stale trace sessions using Admin Studio.

Related articles

Managing requestorsTracer event queue overflowsAdjusting the buffer size of the Tracer headerReducing Tracer event output

Tags

Pega Platform 8.4 Low-Code App Development

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us