This may be related to Missing recordings for a conversation, but I experience a slightly different behaviour.
I am attempting to build a deep integration with Genesys platform metadata and voice recordings. In a nutshell, I am experiencing the following perculiarity (Java Genesys Client):
-
search for conversation by date (/api/v2/analytics/conversations/details/query)
-
I follow up for each result found with a call to get all recordingMetadata (api/v2/conversations/{conversationId}/recordingmetadata
-
At this point, on cold start querying for a date in the past with known data, I often find no results. However, if I wait a few seconds and try again, I may find recordingMetadata that I know is there. Or, sometimes, I may not.
-
If I wait some period of time (maybe an hour or so), I can repeat this whole experience.
This doesn't feel like eventually consistent issues....this feels more like the population of an intermediary cache which takes longer than some fixed query timeout. Is there any way to mitigate this, specify an alternate query timeout, or something along these lines? This apparent behaviour makes time based integrations problematic, as "Not Found" doesn't really seem to mean "Not Found".