Direct Query Quirk, Unintended Feature or Bug?

When using Direct Query on an Oracle db for on premise data there seems to be behavior in the report that I technically understand but do not understand from a feature of the application.

What I have experienced is when a report loads the data refreshes (good), if the user interacts with the report by say selecting a bar in a tile or using a slicer, the data refreshes. The issue, is that if the selected item is then de-selected, the dataset reverts to what appears to be the cached version of the dataset when the report loaded. I can understand why this happens technically, but from a user’s perspective, this behavior will no doubt cause confusion.