Lightroom Classic has sync errors for photos that have Generative AI remove

I had the same problem with Gen Ai removal on images that were stuck in sync. Regenerating the AI part of the images solves the sync issue. But if you have many images, this can be tedious.

Hi ​@defaultynovrsqmy403,

Thank you for reproducing this again and for capturing the Diagnostic Report while the photo was stuck. The AuxMissingError and missing auxiliary-file IDs are particularly useful, especially since another user is seeing the same error.

Before changing or regenerating any of the Generative Remove edits, could you try one small test on the affected photo?

With the photo still stuck in sync, make a very small non-AI Develop adjustment, for example, change Exposure by +0.01, and then give Lightroom a little time to sync.

Please let me know whether:

• The photo begins syncing successfully after that small edit, or
• It remains stuck with the same sync error.

Also, could you send me the complete Lightroom Classic Diagnostic Report ZIP from this failed-sync session? Please upload it to Google Drive, Dropbox, WeTransfer, or a similar service and send me the download link via DM rather than posting the logs publicly.

Thanks again for all the careful testing. This is giving us a much more specific reproduction to take back to the Lightroom Classic team.

Best,
Anshul Saini

Same issue here. I remove the Subject masks, or the generative deletion, and the images have been properly synced. It’s a bit of an annoying bug. 😌 thanks for your help ​@Anshul_Saini 

When I rung a diagnostic report, I see the same error as ​@Gunela, and details of missing aux ids.

I'm experiencing what appears to be the same issue with Lightroom Classic on macOS.

I'm currently synchronizing a collection of wedding photographs, and the synchronization is stuck with 146 images pending.

Lightroom Classic reports 17 photos under "All Sync Errors". All 17 belong to the same folder and have been edited using Generative Remove.

I've also checked several photographs that have synchronized successfully, and none of those had Generative Remove applied.

I generated a Lightroom Classic Sync Diagnostic Report, which repeatedly shows the following error:

403 – AuxMissingError

The server response states:

"Some of the aux files are not uploaded which is required for rendition generation."

All affected photographs are accessible and can be edited normally in Lightroom Classic.

This strongly suggests that the synchronization failure may be related to missing auxiliary files associated with Generative Remove.

I haven't reset the synchronization data or modified the affected photographs, so the original error state is still available for investigation.

I can provide the complete diagnostic report if needed.

Is this a known issue currently being investigated by the Lightroom Classic engineering team? Is there a recommended workaround that preserves the existing Generative Remove edits?

Hi @defaultynovrsqmy403,

Thanks for the detailed report and for narrowing this down specifically to photos containing Generative Remove edits.

The Lightroom Classic team is already investigating related sync issues involving AI-based edits. Your workflow is particularly useful because the problem occurs when photos with existing Generative Remove edits are subsequently added to a synced collection.

If you still have an affected photo in Catalog > Sync Errors, could you please leave it in that state for now and share:

• A screenshot showing the exact Sync Error.

• Help > System Info > Copy & past here.

• The original file type (CR3, NEF, ARW, DNG, etc.).

• Whether the Generative Remove edits were created in Lightroom Classic or another Lightroom app.
  
  

There’s no need to regenerate additional Remove objects or use Rebuild Sync Data for now. The original failing state may help us determine whether this matches the issue already under investigation.

I’ll also share your specific workflow with the product team.

Best,
Anshul Saini