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

INFO_FORCED messages in the log files



For each email sent, the following message is generated in the logs:

[http-apr-8080-exec-4] [TABTHREAD2] [ ] [CEMIns:01.05] (lAttachments._baseclass.Action) INFO| [email protected] - In @baseclass.SendEmailWithAllAttachments

Since it is a debug message, it should not appear in the logs. It may cause the logs to grow rapidly when many email messages are sent.

The SendEmailWithAllAttachments activity on Work- level does not log this information. However, the rule on @baseclass logs the information with INFO_FORCED logging level.

Error Messages

Not Applicable

Steps to Reproduce

Send an email with attachments.

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-40834.

The hot fix changes the logging level from INFO_FORCED to INFO.

Change the SendEmailWithAllAttachments activity's logging level when the default logging level must be INFO and is required to remove the log messages.

Open the respective activity's Java code ("Action" >"Show Java") to retrieve the name of the logger to re-configure.

The following line in the Java code contains the corresponding logger name,

private static final LogHelper oLog = new LogHelper(...);

The argument for the constructor is the name of the logger, in this case, 'Rule_Obj_Activity.SendEmailWithAllAttachments._baseclass.Action'.

However, INFO_FORCED cannot be switched off using this method.

Published July 23, 2018 - Updated October 8, 2020

Was this useful?

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