Metadata extraction failing on external library, causing phone backup photos to get stuck in upload
Hi Team,
I appear to be having some issues with the metadata extraction. If I perform an "all" extraction job, at some point it will get stuck while going through my external library, and no longer continue, with the number pending not decreasing and I have to eventually cancel the process.
I've noticed that "some" of my photos get stuck in the upload folder and are not moving into the storage template folder. Checking logs it seems immich was unable to extract metadata. If I extract metadata manually by going into the photo on immich web and selecting the option to "refresh metadata" then the file moves into the correct storage template folder.
My question is, is this issue being caused by the metadata engine not working due to getting stuck in the external library scan? Or some other bug. Is there a way to allow the process to continue even if the module comes across metadata it cannot read? If I remove the external library and do a metadata scan, then do a storage template migration all items that are remaining in upload are scanned correctly and the storage template migration works to move the items into the storage template folder.
Is there something I'm doing wrong?
I appear to be having some issues with the metadata extraction. If I perform an "all" extraction job, at some point it will get stuck while going through my external library, and no longer continue, with the number pending not decreasing and I have to eventually cancel the process.
I've noticed that "some" of my photos get stuck in the upload folder and are not moving into the storage template folder. Checking logs it seems immich was unable to extract metadata. If I extract metadata manually by going into the photo on immich web and selecting the option to "refresh metadata" then the file moves into the correct storage template folder.
My question is, is this issue being caused by the metadata engine not working due to getting stuck in the external library scan? Or some other bug. Is there a way to allow the process to continue even if the module comes across metadata it cannot read? If I remove the external library and do a metadata scan, then do a storage template migration all items that are remaining in upload are scanned correctly and the storage template migration works to move the items into the storage template folder.
Is there something I'm doing wrong?
