Cannot find session I/Os

In Cloud Invantive I would like to monitor my API calls.

Following your explanation, I understood that this is done by going to Session I/Os and then filtering on the data container ID of the database that has been refreshed.

Despite seeing that a refresh has just taken place, I am unable to find the Session I/Os.

This concerns data container ID https://start.exactonline.nl/33457955.

I would appreciate some information on why this is happening and how I can properly monitor the API calls.

Advice is to check the screen again (see also Welke API calls heeft Invantive UniversalSQL daadwerkelijk uitgevoerd?).

It may take some time before the data becomes visible. In practice, it should be visible within 10 minutes. The data will then remain visible until around 0:00 UTC the following morning. After that, the data moves to long-term storage. There is also a storage area with monthly totals, which can be viewed via “Monthly Aggregated Session I/Os”.

Upon checking, it appears that the last recorded Session I/Os on this data container ID are from 2 September 2025.

Please note that the new product Invantive UniversalSQL Server does not currently record any visible session I/Os.

Tried again today. Refreshed the datasets today and only fetched the Session I/Os after a while.

I still don’t see any Session I/Os even though the datasets have been refreshed.
They’re updated every day anyway, so it’s odd that the last one visible is from 2 September.

Has something changed here?

When querying the table ExactOnlineREST..Items (via the UniversalSQL editor on Invantive Cloud), the corresponding API calls are visible on the Session I/O’s screen.

However, the session I/O’s from a query of ExactOnlineREST..Journals (via OData4) are not visible on the Session I/O’s screen. The data is also not visible to the administrator.

Further analysis is needed to determine the cause of the Session I/O’s not coming through.

An improvement has been rolled out into production, meaning session I/Os are now visible again for both on-premises and online systems using Invantive UniversalSQL 24.0.

Please try again.”}

This question was automatically closed after 1 week of inactivity. The last answer given has been marked as the solution.

Please ask a new question via a separate topic if the problem occurs again. Please include a link to this topic in the new question by pasting its URL into the text.