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

Log Level Settings set to OFF not suppressing InfoForced logging



Setting logging level to OFF for a particular activity do not suppress the InfoForced log messages appended by using the Log-Message method in the Activity with InfoForced logging level specified.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create an activity and add a log statements using Log-Message Method and set the LoggingLevel as "InfoForced".
  2. Set the logging level for the activity in to OFF.
  3. Run the Activity.

Root Cause

Expected Behavior


Here’s the explanation for the reported behavior:

Here is the excerpts from the Help document

If you choose InfoForced, a message is added to the Pega log each time the method executes, independent of settings in the prlog4j2.xml file or settings through the Set Logging Levels tool.

To reduce clutter in the Pega Log and improve performance, be sure to remove such InfoForced steps, or convert them to comments, in production systems.

When debugging is complete, you can delete the steps that use this method or change them to comment steps. This is needed for steps where LoggingLevel is set to InfoForced. For others, if the prlog4j2.xml setting for the Rule-Obj-Activity class is higher than the LoggingLevel parameter, executing this method does not update the Pega log and does not affect performance.

Published April 12, 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