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.