-
-
Notifications
You must be signed in to change notification settings - Fork 172
Closed
4 / 44 of 4 issues completedDescription
The current implementation of immich's background jobs has some problems. It happens frequently that asset update trough the API interferes with a job performed in the background. The job fails or the API call fails.
API files gives "Internal Error 500" that are sometime irrecoverable by Immich-go
The feature "Storage Template" increase the problem a lot. The files are moving to another place when the API tries to update something.
See related issue on Immich:
- Race Condition in File Processing - Files Being Moved Before Metadata Extraction immich-app/immich#17954
- [API] tagAssets doesn't tag all assets randomly immich-app/immich#16747
Possible mitigations:
- Call the API only when it is required. Ex: don't call the API to change the date of capture that is present in the metadata
- Delay API calls to give a chance to Immich to complete the storage move
- Disable the storage template feature while uploading and re-enable it at the end
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels