Noticing a timestamp mismatch when fetching conversation history. The apiV2ConversationsList endpoint returns the modifiedDate as 2024-05-20T14:30:00.000Z, but the apiV2AnalyticsConversationsQuery payload shows 2024-05-20T14:31:15.000Z for the same conversationId.
GET /api/v2/conversations?conversationId=abc-123
// Response: { modifiedDate: "2024-05-20T14:30:00.000Z" }
POST /api/v2/analytics/conversations/query
// Body: { where: [{ path: "conversation.id", op: "eq", value: "abc-123" }], groupBy: [] }
// Response: { data: [{ modifiedDate: "2024-05-20T14:31:15.000Z" }] }
The analytics endpoint seems to pick up post-processing events or queue movements that the real-time endpoint ignores. Is there a documented rule for when to prefer the analytics store over the live API for historical lookups, or should I always stick to conversations/list to avoid this drift?