Skip to main content
Participant
June 9, 2025
Question

Issue with healing tool

  • June 9, 2025
  • 1 reply
  • 182 views

Need your expertise on Lightroom…

I’ve been dealing with an annoying issue in my workflow for the past few weeks and wanted to ask if any of you have experienced this too—or even better, found a solution for it.

 

I edit my photos as usual with Imagen AI, and then I fine-tune them in Lightroom—mostly using the Healing tool (for blemishes, etc.). So far, so good.

But as soon as I switch to the next image and then go back to the previous one, all the retouching is gone. It looks like it’s reverted to the state right after the Imagen edit—without my manual adjustments.

 

What’s weird is that a red dot appears on the Healing tool with a note saying, “Some settings need to be updated.” I can click to update, but the whole thing is really frustrating because it means I have to redo everything. And it happens again every time I switch images.

 

Has anyone else had this problem or maybe even found a fix for it?

The current situation is seriously slowing down my workflow and making editing really inefficient.

 

Thanks in advance for any feedback or help!

1 reply

JohanElzenga
Community Expert
Community Expert
June 9, 2025

Updating AI masks is normal after you've used the healing tool. What is not normal is that you would have to update the healing edits (and consequently the masks) after going from one image to another. That sounds like perhaps the following problem, that has been reported quite a few times: Lightroom Classic stores AI masks and other AI data in 'Catalogname.lrcat-data'. Sometimes this file (Mac)/folder (Windows) gets corrupted, or the permissions are getting set wrongly, so Lightroom Classic cannot write to it. That explains what you are seeing. The easiest method to solve this is to move 'Catalogname.lrcat-data' out of your catalog folder, so Lightroom Classic will rebuild it. That means you will once again have to update the AI settings for all AI-edited images, but then the problem should not reoccur anymore. You can trash to old 'catalogname.lrcat-data' if this indeed solved it.

 

-- Johan W. Elzenga
Participant
June 9, 2025

 

 

Thank you very much for the tip.

I’ll test it next weekend and see if it works. A few weeks ago, it was working without any problems, so it would be plausible if that’s what’s causing the issue. Right now, I’m still on vacation and don’t have access to my Mac.

I’ll let you know whether it worked.