Caching of k8s objects in Lens

Hi all,
We have an audit policy in our cluster to audit access to specific k8s objects.
We have noticed that while for example accessing (verb GET) an object via kubectl, there is a corresponding real-time audit trail. The same does not hold when we access the same object via the Lens UI.
Does Lens pre-load and cache objects in the background and if so is there a way to control this behavior?