Question: `scan` results with latest changes

[chenkasirer]

We're developing an application which uses immudb to store its runtime data as key-value pairs.
For monitoring purposes we use scan to periodically grab the contents of the database and display them.

However, scan seems to not always return the latest state of the data. I'm sure this is by design and has to do with the immutable nature of the database.

scan with sinceTx goes in the direction we're looking for but we don't always have access to the latest transaction ID, since there are multiple clients running in different processes.

Is there a way to "force-commit" before calling scan? some way of blocking for x seconds to wait for executing transactions? or any ther way to make scan return the lastest data state.

Thanks!