Lightroom Classic 15.4.1 – AI Edits Storage Error – AI masks and Generative Remove edits disappear
I am having a serious problem with Lightroom Classic 15.4.1 on Mac.
Lightroom displays the following error on startup:
“AI Edits Storage Error – There was a problem updating AI edits in Lightroom. Future AI edits may not be saved and may be lost.”
The problem is affecting AI edits across different imports/catalogued photos.
Examples:
- I use Imagen AI and its Background Mask beta feature. Lightroom shows that the mask exists, but the actual masked area is missing.
- When I click the AI update button, Lightroom recalculates the mask correctly.
- I can then edit the mask, for example by changing exposure.
- After leaving the photo and returning later, the actual mask selection has disappeared again, although the mask entry itself is still present.
- I also used Lightroom's AI Remove/Generative Remove tool. The removal looked correct initially, but later the removal was gone again.
- Updating 10 images in bulk takes a long time, but the AI masks are still missing afterwards.
Lightroom has also become extremely slow.
I also receive an error when Lightroom tries to create a catalog backup:
“Lightroom cannot create a backup of the catalog…”
I have 106.56 GB free on a 499.96 GB internal SSD, and I confirmed that Lightroom can write to the backup folder manually from Finder.
I optimized the catalog successfully and restarted Lightroom, but the AI Edits Storage Error remains.
My active catalog is:
Lightroom Catalog-2-v13-3
The catalog files are:
.lrcat = 1.39 GB.lrcat-data = 2.49 GB
I have already made a separate copy of both files as a safety backup.
Most importantly: I have a wedding catalog with approximately 650 photos and I am already halfway through editing it. I absolutely do not want to lose those edits or revert to an older catalog unless there is a safe way to preserve my current work.
What is the safest way to repair the AI Edits Storage Error without losing the existing catalog edits or the AI edits that are still intact?
Is there a supported way to repair/rebuild the .lrcat-data storage, or should I contact Adobe Support directly?
