could someone explain the variance between the architect flow performance dashboard and the analytics api v2 endpoint for conversation counts?
the organization is running a BYOC setup in eu-west. the flow ‘ivr_main_routing’ shows 1,240 interactions in the 24-hour period ending 2023-11-15 23:59:59 utc according to the web ui flow performance view. however, the api call to /api/v2/analytics/conversations/details/query with the same date range and filter for flowid returns a total count of 1,195.
the discrepancy is approximately 3.6%. the query parameters include start and end times in iso 8601 format, along with the specific flow id. no additional filters are applied. the dashboard metrics are critical for billing reconciliation with our vendor, so accuracy is paramount.
is there a known delay or aggregation logic difference between the ui cache and the api data store? or should the api be considered the source of truth? the environment details are standard genbys cloud, version 10.5. the issue persists across multiple flows, suggesting a systemic reporting difference rather than a single flow configuration error. any guidance on aligning these figures would be appreciated.