Racy /api/v2/logs vs /api/v2/users/{}/logs

Hi, it seems /api/v2/logs?from=.. API is racy, it doesn’t return all entries since the checkpoint in case the latest events are recent. This is even moreso confusing because /api/v2/users/{}/logs does seem to return up-to-date logs. Is this problem specific to the ?from=.. API? How can we make sure that the logs returned are up to date?

Hi there,

Thank you for reaching out to us!

We are trying to reply and provide information to older posts, in case others find it useful as well.

This was also reported internally and our Engineering team has looked into the issue with the conclusion of a caching delay. It seems like when a user is created, it is indexed in the search database which can cause a slight delay in the search results.

For the time being and until an update is pushed on this matter ( we do not have any ETA or information if this ie being worked on currently), please use /api/v2/users/{}/logs instead if this works the correct way for your use-case.

Have a great one!
Gerald