OQL Non persistent Garbage collection

Hi All, In the main page of my application I use several OQL request list overviews. With an associated search entity. These OQL lists are displayed on the screen via a Non persistent entity.   When using the search, after a while I get the message: Request state size of xxx objects exceeds the threshold of 100 objects. (and keeps adding up)   I think this is because a new request via OQL to the list leaves old data in memory? How can a Non Persistent entity completely be cleared before I make a new request?
1 answers

This issue is caused by the request state size that exceeds the configured threshold. There is documentation available on how to act: