quick question about the behavior of the ai/bots conversation export endpoint when queried from a multi-org premium app context. we are building a unified analytics dashboard for enterprise clients who have split their workforce across several distinct genesys cloud organizations but manage them through a single appfoundry integration. the goal is to retrieve detailed conversation transcripts and bot interaction metrics for compliance reporting.
we are using the standard platform api endpoint /api/v2/analytics/conversations/details/queue with a custom query definition. the issue arises when the query spans multiple organizations or when the date range exceeds 30 days. instead of returning a fully populated json object with the expected responses array containing id, version, and detailed transcript objects, the api returns a truncated payload. specifically, the transcript field is often empty or contains only the first few turns of the conversation, and the botDetails object is missing entirely for interactions handled by the virtual agent.
we have verified that the oauth tokens used for the requests have the necessary analytics:read and ai-bot:read scopes. the rate limiting headers (x-genesys-cloud-ratelimit-limit) show we are well within the limits, so throttling is not the cause. the error is not a http 4xx or 5xx status; the response code is 200 ok, but the data integrity is compromised. this makes it difficult to audit bot performance accurately across the multi-org structure.
is there a known limitation with the conversation export api regarding multi-org queries or large date ranges that causes this data truncation? we are considering switching to the streaming api or using the batch export feature, but we need real-time data for our dashboard. any insights on the correct approach to retrieve full bot conversation details in this specific multi-org appfoundry scenario would be greatly appreciated. we are currently using the java sdk version 12.5.0 for our integration.