Stuck on pagination logic for the analytics details endpoint. We’re pulling conversation data for our custom DFO channel reporting. The docs suggest using the cursor parameter for large datasets, but it’s behaving unexpectedly.
Here’s the flow:
- Initial call returns
nextUri. - I extract the cursor from that URI.
- Pass it back to
/api/v2/analytics/conversations/details/query.
First few iterations work fine. Then it just hangs or returns the same set of messages. No error code, just a timeout or duplicate data.
const response = await axios.get(nextUri, {
headers: { 'Authorization': `Bearer ${token}` }
});
Is the cursor tied to a specific time window? If the data is still streaming in, does the cursor invalidate? We’re seeing this when pulling real-time-ish data for active DFO sessions. The page-based approach feels safer but limits us to 1k records. Anyone else hit this wall with cursor pagination on conversation details?