Why are collection endpoints' "since" timestamp inclusive?

[p3v9d5ui]

This may not be the best place to raise this issue, because the problem is with the underlying REST API, and not this node.js client, but I'm not aware of any other Pipedrive developer forum or issues list. Please let me know if there is a better place to post this issue.

The beta collection endpoints, such as /v1/persons/collection have a since parameter which filters objects created or updated since that timestamp, but the match appears to be inclusive, unlike other endpoints like /v1/recents which has an exclusive since_timestamp.

This is a problem, because with most APIs, one can always use the timestamp of the last object fetched from the previous page as a type of cursor for fetching the next page of data. But since since is inclusive, the result set will always include that last previous object. And worse, if a page of results happens to have objects with all the same timestamp, then one cannot advance the cursor.

Is this a known issue?

[github-actions]

This issue has been marked as stale due to inactivity. It will be closed in 30 days if no further activity occurs.