You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update external assets are aggressively cached in web #6955
When updating an external asset and refreshing the library, there is very aggressive caching on the web that prevents it from being shown to the user. This caching works fine for upload libraries but not external libraries.
We need to be smarter about caching external assets.
This is a known issue and is documented in the external library docs but we should still fix it
The OS that Immich Server is running on
N/A
Version of Immich Server
v1.94.1
Version of Immich Mobile App
N/A
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
-
Your .env content
-
Reproduction steps
1. Scan external library
2. Change metadata of an asset
3. Rescan
4. Nothing changes in web view
there is a lot of failed cache invalidation in immich, and idk how it should be fixed
another example that comes to mind is when a person thumbnail is changed, it changes the thumbnail on that person's page yet going back to the /people page shows the old thumbnail
but yes, i've also had this problem where i transcoded an incompatible video, and after jobs completed, immich asset viewer didn't see the new version of the video for a while so wouldn't play it
Activity
pyorot commentedon Jun 22, 2024
there is a lot of failed cache invalidation in immich, and idk how it should be fixed
another example that comes to mind is when a person thumbnail is changed, it changes the thumbnail on that person's page yet going back to the /people page shows the old thumbnail
but yes, i've also had this problem where i transcoded an incompatible video, and after jobs completed, immich asset viewer didn't see the new version of the video for a while so wouldn't play it
etnoy commentedon Apr 1, 2025
I'm not sure we should close this one, I think this issue is the catch all for cache invalidation. Let's make the other issues a dupe of this one
danieldietzler commentedon Apr 1, 2025
@etnoy It's not just about external libraries though. So this issue doesn't tell the whole story. The other one is more generic IMO