Hey guys
We are trying to pick up the data from Genesys Cloud using analytics API
NodeJS, mainly.
-
The extraction happens every hour for the period of the past 2 hours.
This way we are able to upsert new ones and modify those that have changed their state within the required period of time. -
The query is correct and does not contain special features like "conversationEnd"-exists
This way we are sure to pick up all the calls that have changed the state -
The extraction for the past 2 hours is launched roughly 30 seconds after the period is finished
example: for the data between 12 and 13:00 we would start the code at 13:00:30
The problem is...for many extractions of this sort, we are missing roughly the past 30 minutes of data and yes, we pick up the data in the next peiod but then we are missing out on the next 30 minutes and so on and so forth
Our first guess was that we defined the query wrong. But after verifying it in different ways we are sure that it is correct.
Question:
Why can we potentially miss out on the active data?
-
Should we maybe wait for longer in order to data to be properly registered in Genesys?
If so, how can you explain that async Job for this period can return FULFILLED with no issues? - If you have any other solutions or ideas, please let me know where I can look for it
- How much time does Genesys need to register a conversation in a classic way and store it in its database?
