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

Commit cannot be performed when process is run from SLA



After upgrade from PRPC 5.5 to Pega 7, users are receiving an access denied error when the work object is processed via the ServiceLevelEvents agent.

If processed manually, the work object is processed successfully.

Error Messages

Current user is not authorized for 'Modify' access for Rule-Obj-Class ClassName

A commit cannot be performed because a deferred save of instance InstanceName failed

Steps to Reproduce

  1. Create a work object.
  2. Process it via the ServiceLevelEvents agent.

Root Cause

An issue in the custom application code or rules.

No access group that the
ServiceLevelEvents ​agent would use has the privilege to modify classes derived from CommonApps-.


Add a privilege to a role common to all the access groups that allowed modification of CommonApps-.

Published May 24, 2017 - 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