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

Tracer session error: session does not exist when tracing agents

SA-18669

Summary



An error occurs every time when tracing an agent.

Error Messages



Please restart Tracer because Tracer session error: session your_session_id does not exist

Steps to Reproduce

Trace an agent from the SMA.

Root Cause



Not Applicable.

Resolution



Here’s the explanation for the reported behavior:

That is the expected behavior when tracing agents, for example, an SLA. Once user receives that warning or notification when the activity finishes and the requestor is returned to the pool, this is not a problem if everything else is working correctly.
 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

16% 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