In new content fragment editor the auto save is not working

[senthilnetwork]

on AEM Cloud, we have many CFs that were created through the AWS upload tool process.
Nowadays, if I try to update one of those uploaded CFs using the AEM Cloud CF New editor interface, the Save will fail on the CF and I can't do a Save on the CF. I have to move to the Old Editor to make my change. In the Old Editor, I can make my update, save, then publish.

Not sure if this is because of the CF New Editor ? any suggestion...

[giuseppebag]

The new CF editor enforces stricter validation rules than the old editor. Open the browser's developer console (F12) when attempting to save and check for specific validation error messages that may reveal which fields are failing validation.

CF created through bulk import tools may not have complete metadata (see empty required fields) or validation attributes that the new editor expects. The old editor is more lenient with missing or incomplete field data, while the new editor validates against the CF model more strictly.

If you save a CF using the old editor, does the new editor allow autosaves, or do you continue to encounter validation failures? 

If so, try creating a test case comparing a fresh CF created manually versus one from the AWS bulk import tool to identify exact structural differences. 

https://meticulous.digital/blog/f/migration-to-the-new-content-fragment-editor-in-aemaacs?blogcatego... 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/content-fragments-console/editor...

[VishalKa5]

Hi @senthilnetwork ,

This issue happens because the new Content Fragment Editor in AEM Cloud is stricter about the fragment’s structure and metadata format. The CFs uploaded through your AWS upload tool likely have missing or invalid metadata (like variation, model, or data type mismatch) that the new editor can’t handle, causing the auto-save or save to fail.

Open the same CF in the old editor, check and correct any broken model references or invalid fields.

If needed, re-save or re-create the CF using the correct Content Fragment Model.

Adobe also recommends using the old editor temporarily for such legacy CFs until they’re cleaned up or reimported properly.

the save issue isn’t a bug but a data compatibility issue between your old CF structure and the new editor’s validation rules.
Thanks