Genesys Cloud - Main

Hey Everyone,

Background:- We are using AWS platform to land Genesys API responses and EventBridge (Live Topic) data for our reporting needs. To get almost live data for STA transcript we are using this Live Topic  "v2.conversations.{id}.transcription"  and as soon as we get message in AWS SQS service for that topic we are calling this API End point "/api/v2/speechandtextanalytics/conversations/{conversationId}/communications/{communicationId}/transcripturl".

Issue:- We observed error 404 (Object not found) while doing real time call to the API as soon as that live topic provides parameter for API payload request. If we wait for some time and try again we get status 200 out of mentioned API end point.

Question:- In community experience using same approach what is the best latency we can add to call the same API end point after getting Live Topic message ? I mean should we always wait for 5 mins after getting LiveTopic message to call the API  and that will make sure we get 200 in all cases (even for very lengthy conversation) ?

Please share your experience and suggest best latency period. The aim is to stay near real time possible without load catch build up.

Thanks,

Jignesh

Hi Jignesh,

I don't think there is a documented minimum time before the transcript becomes available as it is probably depends on how long it takes to process it.  Maybe others in the community can share their experiences.

There is more information available here: Transcription Notifications

Hey Everyone,

Background:- We are using AWS platform to land Genesys API responses and EventBridge (Live Topic) data for our reporting needs. To get almost live data for STA transcript we are using this Live Topic  "v2.conversations.{id}.transcription"  and as soon as we get message in AWS SQS service for that topic we are calling this API End point "/api/v2/speechandtextanalytics/conversations/{conversationId}/communications/{communicationId}/transcripturl".

Issue:- We observed error 404 (Object not found) while doing real time call to the API as soon as that live topic provides parameter for API payload request. If we wait for some time and try again we get status 200 out of mentioned API end point.

Question:- In community experience using same approach what is the best latency we can add to call the same API end point after getting Live Topic message ? I mean should we always wait for 5 mins after getting LiveTopic message to call the API  and that will make sure we get 200 in all cases (even for very lengthy conversation) ?

Please share your experience and suggest best latency period. The aim is to stay near real time possible without load catch build up.

Thanks,

Jignesh