Why do components use the old name of content fragments even though they were renamed?

[smckinley]

We renamed some content fragments but when we go to the component using those fragments, the old names still appear. What can we do to refresh them? Please help! 

[SantoshSai]

Hi @smckinley,

Mostly likely becuse of stores the reference metadata.

Here is what you can do: 

1. Check if the path actually changed

Go to CRXDE Lite or use Developer Mode -> Inspect the component.

• Look for the property that references your CF (usually something like fragmentPath or fileReference).

• If it still points to the old path, you’ll need to manually reselect the CF.

2. Re-link the fragment

Edit the component in author mode -> re-open the Content Fragment selector -> choose the newly renamed fragment.
This refreshes the stored path and updates metadata references.

3. Clear caches

If you’re using GraphQL models, Content Fragment Lists, or Experience Fragments:

• Clear or invalidate the cache.

• For AEMaaCS, you can also use /_api/graphql cache flush from Developer Console.

4. Republish the renamed fragments - Sometimes the publish environment still holds the old metadata.

5. Just in case Run a query to find old references

If you renamed multiple CFs and need to bulk fix them:
Use a QueryBuilder query like:

path=/content
property=fragmentPath
property.value=/content/dam/old-folder-name
p.limit=-1

Then update references via Groovy script or manually.

[Syed_Shaik]

Hi @smckinley 

Verify if the CF path changed

• Open CRXDE Lite or Developer Mode → Inspect Component.

• Check the property that stores the CF reference (like fragmentPath or fileReference).

• If it still points to the old name/path, you’ll need to re-link the fragment.

• Re-link the updated fragment

  • Edit the component in Author mode.

  • Open the Content Fragment selector and reselect the renamed CF.

  • This forces AEM to refresh the reference and metadata.

• Clear any caches

  • If your component or model uses GraphQL, content fragment lists, or experience fragments, clear the GraphQL cache.

  • On AEM as a Cloud Service, you can trigger cache invalidation using the Developer Console or the /_api/graphql flush endpoint.

• Republish fragments

  • Republish the renamed CFs to ensure both the author and publish environments have the latest metadata.

• (Optional) Find and fix old references

  • If several fragments were renamed, run a Query Builder query to locate outdated references

[muskaanchandwani]

Hello @smckinley 

Which component is being used to reference the Content Fragment? OOTB or custom?

In AEM 6.5, if the fragments were renamed using the Move option in Assets, only the node name (path) is updated - the Title (jcr:title) remains unchanged. So the components referencing the fragment may still display the old title.

Where exactly you’re seeing the old name wrt the Component?