By chance I prepared two files that are almost identical. All that changed was the name of one column.
If realized that if I open one file, and then I rerun the app and open the other file, the cache does not “see” the difference, thinks that it is still the first file (that has a different column name) and the app fails.
I guess this is more a curiosity than a real problem because (i) probably files will be more different than this and (ii) maybe using the uploader widget to load a new file automatically “tells” the cache that there is a new file.
However since my two files are (a tiny bit) different, they should have a different hash, and I was surprised that I had fooled the cache.
Do you have two files that you can provide that demonstrate this behavior? It’s hard to answer questions like these, since the answer could easily be that you found a bug of some sort.
In general, getting a cached result happens when the exact same arguments are provided to a function. In the case of loading data, literally anything other than the same exact file should trigger a re-run.