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

Cases roll back due to Commit failure

SA-79227

Summary



Cases roll back when the ServiceLevelEvents agent resumes the flow from an assignment. When a dummy assignment is added later in the flow, the cases execute successfully.


Error Messages



com.pega.pegarules.pub.PRAppRuntimeException: Caused by trying to calculate the handle of a class whose instances may not be written to the database: Assign-: code: SQLState: Message: 
at com.pegarules.generated.activity.ra_action_resumeflow_791448c90bc318018f58d1da9f2aca95.step7_circum0(ra_action_resumeflow_791448c90bc318018f58d1da9f2aca95.java:627) ~[?:?]



Steps to Reproduce

  1. Create a flow with a Service Level Agreement (SLA) specified on an assignment.
  2. Configure the SLA rule to resume the flow.
  3. Run the process and wait for the ServiceLevelEvents agent to execute the case.


Root Cause



A When rule is present that referenced the newAssignPage after the assignment is already completed. As a result, the page is created using the class specified on the Pages & Classes tab. An error occurs when this page is saved since it is created with the Assign- as the class.


Resolution



Perform the following local-change:

Modify the When rule to check if the newAssignPage exists before referencing it. 

Use the following function: @PageExists("newAssignPage").

 

Suggest Edit

Published August 15, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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