コミュニティアチーブメントバーを展開する。

Submissions are now open for the 2026 Adobe Experience Maker Awards.
解決済み

Issues with updating segment UI

Avatar

Level 5

Hello, we have implemented Context Hub in our project (6.5) and found some issues related to updating the segment UI. Once the segment is created, if you author segmentation components with the values, even though the segment is resolved, the UI does not turn green. We had to refresh the browser to see if the segment is resolved or not. The same issue has been reported in the forum below as well. Basically, rather than refreshing or checking in the browser console, we would like to fix the issue. Please let me know if anyone has encountered a similar issue and what the fix was for it.

http://www.sgaemsolutions.com/2018/12/personalization-using-contexthub-in-aem.html

 

test1234567_0-1729211283848.png

 

Another observation: I see a cache folder (/conf/wknd/settings/cloudsettings/default/contexthub/cache) in the WKND site. I'm just checking if this is required for custom configuration. If so, what is the purpose of it?

test1234567_1-1729212139740.png

 

 

1 受け入れられたソリューション

Avatar

正解者
Community Advisor

Hi @test1234567 ,

This is something which is common in AEM as per the Adobe "All traits are resolved immediately, though most only change on page reload."
For further validation you can look into the network call in browser console which is happening on page load and may be missing during updating the segment.
In he below link you can find a note section where this observation has been added.
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/....

For cache node creation in CRX, the system automatically creates a cache node, which saves the generated kernel.min.js and ui.min.js. 

-Tarun

元の投稿で解決策を見る

1 返信

Avatar

正解者
Community Advisor

Hi @test1234567 ,

This is something which is common in AEM as per the Adobe "All traits are resolved immediately, though most only change on page reload."
For further validation you can look into the network call in browser console which is happening on page load and may be missing during updating the segment.
In he below link you can find a note section where this observation has been added.
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/....

For cache node creation in CRX, the system automatically creates a cache node, which saves the generated kernel.min.js and ui.min.js. 

-Tarun