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

Trace Open Rule feature traces all rulesets



When using the Trace Open Rule feature, Tracer traces everything and does not respond to the settings. It ignores the 'RuleSets to Trace' setting, which causes the browser to crash.

Error Messages

Not Applicable

Steps to Reproduce

1. Open a Rule (preferably JMS or File Listener) and perform Trace Open Rule.
2. Check only one ruleset in the 'Rules to Trace' Section.
3. Observe that Tracer traces all the rulesets

Root Cause

Tracing a service rule would be the same as using the Remote Trace option since you are tracing a different requestor. When performing a remote trace, the system does not take into account your settings on the ruleset list because you are tracing a different requestor. The other target requestor you are trying to trace could have a completely different ruleset stack. Hence, PRPC will trace all rulesets of the target/remote requestor.


One option to prevent the browser crash is to set the “Max Trace Events to Display” to 0 in Tracer. The trace data is saved in the file on the server but not sent to the browser to display. You can then use a Tracer viewing tool to view the trace results.

Here is a link to the Tracer viewer tool you can download from the PDN.

Published July 14, 2015 - 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