Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events

Content Fragment Model Editor missing field/showing empty


Level 2


I have a content fragment model that has 50 - 60 fields in it. After adding some more fields and saved, I opened the model editor and most of the fields have disappeared. I added yet another field and saved again, it became totally empty.

Screenshot 2023-09-14 at 10.29.20.png


All the fields, including the new ones are still available in the content fragment editor though. Refreshing the page, or re-logging into AEM does not help. It is not reproduced in other, smaller content fragment models.



I'm aware of a previous report:



However it's over a year old. My AEM version is 2023.7.12874.20230726T072051Z

Anybody can help me? Thanks!


Update: I managed to delete the last added field in CRXDE, now the model editor is back to the 2nd state (with a small amount of fields showing up).

Screenshot 2023-09-14 at 10.51.24.png

Update 2: after some digging it seems to correlate to the amount of fields. When I have 52 fields, all are displayed. Adding any more would cause some fields to be hidden/corrupted in the editor. With 55 fields the whole editor becomes empty

7 Replies


Community Advisor

Hello @xuny 


Did you notice any errors in logs as well?

Aanchal Sikka


Level 2

Hi aanchal!

Thanks for your answer, and no, there's no error in console log


Level 2


Do you mean this one?
It is a big log. This one below might be related?

14.09.2023 12:37:04.533 [cm-xxx-xxx-aem-author-xxx-xxx] *ERROR* [ [1234] GET /mnt/overlay/dam/cfm/models/editor/content/editor.html/conf/myorg/settings/dam/cfm/models/visualizer-feature-app-content HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
org.apache.sling.api.request.TooManyCallsException: BundledScriptServlet (/libs/granite/ui/components/coral/foundation/form/field/field.jsp)


Level 2

Hi @aanchal-sikka, do you see any way of going further with this issue?