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

Unable to skim flow rules after application update

SA-50367

Summary



Unable to skim flow rules after application update.


Error Messages



<host> server[9071]: [PegaRULES-Batch-1] ERROR com.pega.pegarules.deploy.internal.util.MoveLog - Error: Cannot save record.A commit cannot be performed because a deferred save of an instance of class History-Rule failed: code: <none> SQLState: <none> Message: <none> (RULE-OBJ-FLOW -GALLERYREVIEW PYSTARTCASE #20171204T170631.422

<host> server[9557]: [PegaRULES-Batch-1] ERROR com.pega.pegarules.deploy.internal.restorepoint.HistorySaver - History-Add: database save failed.
Jan 12 08:52:32 <host> server[9557]: com.pega.pegarules.pub.database.BadInputException: Trying to save an invalid page: Trying to save an invalid page: page is not valid
Jan 12 08:52:32 <host> server[9557]: .pxRuleData.pyModelProcess.pyShapes(Wait1).pyCallParams.ActionToTake: pyContinueAfterWait does not exist or is not a valid entry for this ruleset and its prerequisites



Steps to Reproduce



Update from Pega 7.1.9 to Pega 7.3.


Root Cause



A defect in Pegasystems’ code or rules.


Resolution

Apply HFix-40938.



Suggest Edit

Published January 31, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

66% found this useful

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