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

SLA agent generates errors in Pega logs



When the Pega-ProCom ServiceLevelEvents agent processes an assignment record with a Service Level with no escalation activity, a log entry is written to the PegaRULES.log stating that the Activity name not specified for execution in arguments.

Error Messages

Activity name not specified for execution in arguments: {pyClassName=-Work-Interaction-Call, pxObjClass=Rule-Obj-Activity, pyActivityName=} 

Steps to Reproduce

Create a new SLA with no escalation activities.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules logic in step 19 of the ExecuteSLA activity when evaluating blank Goal or Deadline escalation actions.


This issue is resolved in Pega 7.1.6

Published January 31, 2016 - 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