The message is basically saying that AEM isn’t finding any valid offers inside the experience when it tries to sync to Target. In other words, the campaign object it builds ends up empty, so it skips the sync. Since you’ve already confirmed the XF is mapped, published, and bundles are the same acros...

Hi @ChrisPhillipsUC, You can use Groovy Console  -  If allowed, your dev team can quickly write a Groovy script to bulk-move nodes and invoke the PageManager.move() API (which handles references the same way as the UI wizard). Pasting an sample groovy script for you just for reference: import com.da...

Hi @test1234567, I would confirm below checklists: Check XF setup: Ensure your experience fragment variation is properly mapped to an mbox/location under “Targeting” before syncing. Publish the XF: Both the XF and referenced assets need to be published to the Publish instance, then synced to Targe...

Hi @neo-silicon, The clean fix is to let only requests that pass through your CDN reach AEM, and make both Dispatcher and your servlet check for that signal. Here’s the approach I would follow: Put the form “behind the gate.” Have Akamai add a secret header (e.g., X-CDN-Auth) to real browser submis...

Hi @MateuszNo2, Try this:  cache.any /cache { /allowAuthorized "0" # if request has Authorization, don't cache /rules { /0010 { /glob "/content/myapp/us/en/dashboard.html*" /type "deny" } # never cache this path } } clientheaders.any Authorization Cookie (Forward these so Publi...

Hi @EthanRo5, Please check this: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/adobe-summit-2025-complete-aem-session-amp-lab-list/m-p/743780#M49764

Hi @rakesh_mallel, It looks good to me except one thing where I suspect: Can you try to set the configuration property from base_path to base.path (dot instead underscore)? { "enabled":"$[env:ACL_ENABLED;default=false]", "cron": "$[env:ACL_CRON;default=0/50 * * * * ?]", "base.path": "$[env:ACL...

Hi @AnujaRa, I think, HTL tries to adapt from the request by default, but your model is Resource-adaptable. You have 2 options: 1. Make the model request-adaptable (HTL unchanged): @Model( adaptables = org.apache.sling.api.SlingHttpServletRequest.class, defaultInjectionStrategy = DefaultInjectio...

Hi @akhilraj, There are 2 things from your error log 1. Two different user home nodes ended up with the same jcr:uuid. That only happens when concurrent/duplicated creation or a copy/import preserved a UUID it shouldn’t. 2. Two (or more) requests tried to write the same user node/property at the sam...

Hi @Keerthana_H_N, Can you check which index being used with on of the below option? 1. Query Builder Debug (easiest) Open Query Builder Debug:https://<author-stage-host>/libs/cq/search/content/querydebug.html Enter your query params (e.g., path, type=dam:Asset, your property/values). Check Expla...