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

Errors in Production after migrating rules



After a recent code migration of a few rulesets to Production, users are experiencing issues accessing records of a certain class. Instances for that data class are not accessible within the Developer portal and on-screen errors are present.

Error Messages

Status fail
Message There has been an issue; please consult your system administrator
Operator ID OperatorID
Requestor ID H54FE817EF21794E6711D16B690B2D3C6
Timestamp Mon Oct 24 21:18:28 UTC 2016
Engine Version PegaRULES 7.10 ML9 (coreAssemblyCached_719_730)

Steps to Reproduce

Not Applicable 

Root Cause

An issue in the custom application code or rules. Issue is coupled to insufficient access to the target class instances as defined by the role-to-object records coupled to the access groups in question.


Perform the following local-change: 
Update the access group in question to have sufficient access to the classes in question via addition of an additional Role-To-Object instance.

Published October 28, 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