Bug | cache invalidation in the frontend #1197
Description
Right now, we save all outgoing requests to the api in the cache using a web-worker.
It's based on the assumption that all of the data is immutable, so there's no point in retrieving the same information twice.
When the user select recent dated (e.g today's data) this assumption is wrong, so in this case the cache should be quickly invalidated