Event banner
Event details
Is there any news on improving on the "up to 28 and 60 days to update the local client cache"? It is troublesome having to wait this long and it provides and inconsistent user experience. https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/user-information-not-updated?msclkid=dce9c0abc57a11ecbf7fd5c1d653a0b4
- This behavior is by design. Teams has a caching scheme that is designed for capacity and performance optimization. The Teams service caches general user information for up to three days. The Teams client also caches general user information locally. Some data, such as display name and telephone number, can be cached up to 28 days in the client. Profile photos can be cached up to 60 days.
- Hi Stephen. I understand it is currently by design per the link I included in my post. By your restating the content of that doc, Microsoft is basically saying, it cannot feasibly/reasonably improve this functionality and it is not in its roadmap to attempt to do so. Does Microsoft not see how for a collaborative communications tool, this is a somewhat glaring shortcoming in functionality. We have to tell users to plan to update your profile photo up to 2 months ahead of when you want to display the change. This lack of dynamism is disappointing.
Stephen Rosethis is first time I hear any time/dates about the cache. Is there possibilities to get these details in collection? The cache is so big mystery for us.
When you said the cache helps on performance, but have you though if you could implement somekind of "dirty cache" feature? So that you could see when the data in cache is expired? E.g. the profile picture should be quite easy to build so that Teams client see when the picture should be updated on the cache.
