Support Article
RuntimeException: Component stack mismatch
SA-64553
Summary
Post Pega 7.3.1 update, RuntimeException occurs after case creation.
Error Messages
Section 'pyCaseContainer' execution error on page 'pyWorkPage' of class 'AA-BB-CC-DD-EE-FF'.
java.lang.RuntimeException: Component stack mismatch {"NTId":"1528104930394000","NTRef":"cad6e5fe51b09eb67203d77e43dba6f2_39","pyName":"pxNonTemplate"}!!!!===={"paramName":"EXPANDEDSubSectionpyCaseContainerB","liveUI":"data-ui-meta=\"{'type':'Layout','subType':'SECTIONINCLUDE','pgRef':'.pySections(1)'}\"","sectionIndex":"1","isSectionIncl":"true","pyName":"pxLayoutContainer","pyTemplates":[{"pxReferencedId":"b553f0c7838606473d450547a479901e_2","pyName":"pxSection"}]}
at com.pega.pegarules.session.internal.mgmt.autostreams.uicomponent.json.UIComponentRuntimeImpl.finishProcess(UIComponentRuntimeImpl.java:169) ~[prprivate.jar:?]
Steps to Reproduce
- Update Pega 7.1.8 to Pega 7.3.1.
- Create a case through SOAP service.
- After case creation, this exception is coming in log.
Root Cause
This behavior is as per Pega product design.
When the access group on the Service Package and Operator are set with the same service package, the system pages (such as Application page) are not loaded for the better performance of Application and Batch requests.
Resolution
Perform the following local-change:
Include different access group (such as Save As of the access group defined for service package or operator) configured for the Operator or Service Package.
For more information, refer to: https://community.pega.com/support/support-articles/application-page-missing-service-rest-call
Published October 13, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.