Constellation UI rendering issues in Pega 25.1.2

User Experience
1

Hi Team,

we have recently updated our version from Pega 24.1 to Pega 25.1.2 and encountering Pega constellation UI rendering issues with following error messages… and not able to resolve it. Kindly help

It did work correctly in my previous version(24.1) without any issues. Now I am not even able to run new casetype without any forms on it also after the recent update(25.1.2).

Issue 1 log:

[se-nio-5451-exec-157] [  STANDARD] [                    ] [   OfferCon:01.01.01] (ternal.mgmt.StreamBuilderTools) ERROR gtmdev1.ebiz.verizon.com|63.13.47.13 HYYKHZYSHS7OFKCCIBKX81WZT6M3U9JJIA aravra8 - Problem appending stream null 
com.pega.pegarules.pub.PRRuntimeException: Section 'pxOperatorImage' execution error on page 'pyDisplayHarness' of  class 'Data-Portal-DesignerStudio'. : sChecksum is null, Failed to resolve rule file 
	at com.pegarules.generated.html_property.ra_stream_pxoperatorimage_c90cda279ff1eef6801ef8ac79e1d568.execute(ra_stream_pxoperatorimage_c90cda279ff1eef6801ef8ac79e1d568.java:127) 
	at com.pega.pegarules.session.internal.mgmt.StreamBuilderTools.appendStreamKeepProperties(StreamBuilderTools.java:791)
2

Hi Rajesh,

Are you experiencing this issue with all case types and landing screens? Please check console and network tab for any clues.

3

Try regenerating your Routing table and resaving your Constellation DSS.

I have seen post '24 - '25 update these being an issue and this was the most common resolution

4

This rendering error appears after upgrading to Pega 25.1.2 because some internal rule references fail to update correctly, causing a null checksum error when the system tries to load a screen. To fix it, regenerate the Routing table so Pega correctly rebuilds these internal rule connections, then resave the Constellation Dynamic System Settings (DSS) to refresh the UI configuration. This clears the broken links causing the error and restores normal screen loading. This step is the standard fix reported by users facing this issue after upgrading from version 24 to 25.