Conversation
CREDERA
IN
Last activity: 17 Sep 2025 5:03 EDT
Issue with Component Behavior and Configuration Not Reflecting in Real-time Application
My component works as expected in the Community Edition environment, but in the real-time application environment, it is not functioning correctly. Even when I delete or modify configurations, the changes are not reflected; the old component or settings continue to appear.
Could this be related to a caching issue, or are there other possible causes in Pega 24.2?
Details:
-
Component behavior differs between Community Edition and real-time application.
-
Deleted configurations still appear and are not removed as expected.
-
Using Pega Platform version 24.2 Constellation.
-
Have tried clearing browser cache with no success.
Would appreciate guidance on troubleshooting this caching or deployment issue and any recommended steps to force refresh or clear caches fully.
Maantic
IN
@Akhilesh.Madala - Once we upload the component if it is not reflecting, resave the application rule. Once we resave the application rule pega will automatically sync it up.
Regards,
Kalinga
TRUVIQ SYSTEMS
IN
@Akhilesh.Madala please recheck the rule-set name used for publishing, and make sure you have the correct ouath credentials, if possible create a new component,after updating the config with the same code, for real time application environment, and also make sure, API service package is same as your Oauth credentials
Highmark
IN
@Akhilesh.Madala Can be a rule cache issue too, please try restarting the environment.
Arbetsförmedlingen
SE
@Akhilesh.Madala : It needs to sync in the app static server. Are you using the PEGA CDN or is it your own organizational app static? Sometimes syncing also causes this kind of issues. You might need to restart the app static along with app server with DB cache clear.
Phalanx Consultancy Limited
GB
@Akhilesh.MadalaIt is certainly a sync issue. Follow the application rule save approach as stated below and/or saving the constellation related DSS - finally restarting the server as mentioned below. If it still does not work, review the system runtime context to ensure that it points to correct DX component ruleset. At times, it does respect if only major and minor is defined in the application stack. Please note, it may take upto a minute or two for it to sync up. Check the pySyncToConstellation QP execution in the last hour.
Phalanx Consultancy Limited
GB
I meant it does not respect if only major-minor is defined. So DXComponet:01-01-01 instead of 01-01 only.
TRUVIQ SYSTEMS
IN
@BHUVANESH1sir at that case, I think it will warn us during publishing,regarding the ruleset
Phalanx Consultancy Limited
GB
@SAITARUNSANTHOSHN17115422 since major-minor already expands to the remaining patch versions it does not throw error during ruleset validation that happens during publish. But when sync QP tries to sync it after the publish or save, sometimes problem occurs with the system runtime context. Issue mentioned was related to not picking the latest published and since publish was already successful but could not see the latest changes, problem is associated to sync rather than a publish.
TRUVIQ SYSTEMS
IN
@Akhilesh.Madala if you are able to publish the component check the network and console tab under inspect, for any misconfigurations.
1DigitalNL
NL
@Akhilesh.Madala, you can follow the next steps:
- Is the component with the new configuration present on your pega server? It should be a record in the Rule-UI-Component class.
- Is the ruleset / rulesetversion of the component within your application rulesetstack? (PS: branch rulesets are supported to publish your component to, that is what we use)
- Is the dynamic system setting ConstellationSvcURL correctly configured?
- Is the sync to the app static server successful? This is triggered by a declare expression Rule-Application pzPushC11NAssets (when saving the app) or by declare expression Data-Admin-System-Settings pzPushC11NAssets (when saving the DSS mentioned above).
The sync to the app static server can be traced (if you want to be fast, just private edit the declare trigger, set it to 'Execute Immediately', and trace it yourself when saving the application definition or dynamic system setting).
Let us know where you end up.
ING Bank
NL
@Akhilesh.Madala like others already pointed out - the issue is likely because the assets aren't synced with the appstatic service. Best way to verify if your Pega instance is able to connect to appstatic is to run pzStatusC11NCheck activity and look for the REST response code. Should be 200. If it is so, look for browser tab and check for:
1. errors in console, there might be some CSP rules blocking it or,
2. maybe some other error loading component in the network tab -- have seen 400 error codes sometimes and then we raise a Pega INC.