Experience Fragment issue on cloud

[SanaQu]

Hi Community,

I’m facing an issue with Experience Fragments in Cloud.

We are trying to use the same XF across multiple sites. The fragment references are resolving fine on Author, but after publishing, some of the pages show broken references (the XF doesn’t render at all).

The XF is published and available in Publish, The content path looks correct, Replication logs don’t show errors.

Interestingly, if I republish the XF again, it sometimes works — but not consistently.

Has anyone run into this problem where Experience Fragments intermittently fail to render on Publish? Any tips on what could be causing this or what I should check (replication agents, permissions, etc.)?

Thanks for your help!

[giuseppebag]

hi @SanaQu, have you checked the log files for any errors when rendering fails?

[Karishma_begumSh]

Hi @SanaQu 

Broken XF references on Publish usually happen because of incomplete replication, missing ACLs, or dispatcher caching.

Verify XF availability directly on publish.

Try hitting the XF variation URL directly

https://publish-instance/content/experience-fragments/your-xf-path.html

Check the XF URL directly on Publish.

• If missing → republish + check replication logs & permissions.

• If works direct but not in page → clear dispatcher cache / allow XF paths.

Republishing “fixing” it means either replication lagged or dispatcher was serving stale cache.

Hope this helpful 🙂

Regards,

Karishma.

[SantoshSai · Accepted solution]

Hi @SanaQu,

A few other areas might be worth looking into:

1. Dispatcher cache - Quite often XF rendering issues are related to stale or inconsistent cache at the dispatcher. If you flush the cache for the XF path or the page where it’s embedded, does it render correctly afterward? That might explain why it seems to “fix” itself when you republish.

2. Replication queue consistency - Even though logs don’t show errors, it’s possible the XF package didn’t make it fully to all publishers (if you have multiple). Check the replication agents to make sure the XF content is present on every Publish instance.

3. Permissions on XF content - Sometimes permissions applied on the XF folder can cause issues. Make sure the service user that reads the XF has read access in both Author and Publish environments.

4. Path mapping - If you’re using language copies or live copies, double-check that the XF reference in your page matches the right publish path. Sometimes the reference points to the authoring location instead of the published one.

5. Cloud Manager quirks - On AEMaaCS, publishing is async. If your XF has dependencies (images, styles, etc.), they might not all publish together. Try publishing the XF with “Include References” selected so everything gets pushed at once.

If you’ve validated cache + replication and the problem still shows up randomly, I’d suggest raising a ticket with Adobe Support - intermittent issues usually mean something deeper at the infrastructure level.