@DownPW yes, I’ve noticed similar and it is to do with the cache because it is stored in memory and not on disk… However, when I wrote the code, I did allow for a maximum cache age so I’m puzzled as to why this isn’t being honoured. A review of the code is long overdue to be honest, but it’s slipped down the priority list. The fastest way to resolve this in the short term is to perform a daily restart of the service which will flush the cache.

@cagatay Good question, but one that’s likely best answered by the devs themselves. Could easily be done with a simple jQuery regex but that would really just be painting over rotten wood.