Hi,

The regular analytics API only finds conversations that started during the interval (as to the Jobs endpoint that finds all touched conversations). But the jobs endpoint does not always have the data of yesterday, as it could take 48 hours.

As message conversations can span several days and can start one day and continue another day, that regular endpoint will miss the updated conversations.

Does anyone know of a way to get these incremental updates of yesterday without the need to go back and check all conversations of previous days again, just to see if there's an updated one?

Thanks,

Jeroen

That is the problem with asynchronous interactions.  With our iSync and most likely with A3S from Genesys, there is the need to always reconcile conversations that span over days or even weeks as with Email.  The only possible solution is to only report on conversations that have closed sessions or to automatically close sessions each night.  Also, look at the new aggregate API that came out a couple of weeks ago.

Hi,

The regular analytics API only finds conversations that started during the interval (as to the Jobs endpoint that finds all touched conversations). But the jobs endpoint does not always have the data of yesterday, as it could take 48 hours.

As message conversations can span several days and can start one day and continue another day, that regular endpoint will miss the updated conversations.

Does anyone know of a way to get these incremental updates of yesterday without the need to go back and check all conversations of previous days again, just to see if there's an updated one?

Thanks,

Jeroen

Would using AWS event bridge to get the data instead of using the APIs resolve this naturally. Since you will get each of those events as the happen and can then update the data entry as it occurs. 

That is the problem with asynchronous interactions.  With our iSync and most likely with A3S from Genesys, there is the need to always reconcile conversations that span over days or even weeks as with Email.  The only possible solution is to only report on conversations that have closed sessions or to automatically close sessions each night.  Also, look at the new aggregate API that came out a couple of weeks ago.

Hi,

The regular analytics API only finds conversations that started during the interval (as to the Jobs endpoint that finds all touched conversations). But the jobs endpoint does not always have the data of yesterday, as it could take 48 hours.

As message conversations can span several days and can start one day and continue another day, that regular endpoint will miss the updated conversations.

Does anyone know of a way to get these incremental updates of yesterday without the need to go back and check all conversations of previous days again, just to see if there's an updated one?

Thanks,

Jeroen

The challenge wit the event bridge is that you need to be always listening to get all the events. If you're listener application is down for even a short time (intentionally or not) you will create gaps. Event bridge is great for real-time actions, but wouldn't go there for historical reporting

Would using AWS event bridge to get the data instead of using the APIs resolve this naturally. Since you will get each of those events as the happen and can then update the data entry as it occurs. 

That is the problem with asynchronous interactions.  With our iSync and most likely with A3S from Genesys, there is the need to always reconcile conversations that span over days or even weeks as with Email.  The only possible solution is to only report on conversations that have closed sessions or to automatically close sessions each night.  Also, look at the new aggregate API that came out a couple of weeks ago.

Hi,

The regular analytics API only finds conversations that started during the interval (as to the Jobs endpoint that finds all touched conversations). But the jobs endpoint does not always have the data of yesterday, as it could take 48 hours.

As message conversations can span several days and can start one day and continue another day, that regular endpoint will miss the updated conversations.

Does anyone know of a way to get these incremental updates of yesterday without the need to go back and check all conversations of previous days again, just to see if there's an updated one?

Thanks,

Jeroen

Hi Stuart, fairly new to Event Bridge myself, but isn't one of the benefits of AWS event bridge that if the connection goes down the events get queued up and processed when the connection goes back up?

And at least on the Genesys developer centre guide it seems to suggest this approach:

https://developer.genesys.cloud/analyticsdatamanagement/analytics/integration-guide

The challenge wit the event bridge is that you need to be always listening to get all the events. If you're listener application is down for even a short time (intentionally or not) you will create gaps. Event bridge is great for real-time actions, but wouldn't go there for historical reporting

Would using AWS event bridge to get the data instead of using the APIs resolve this naturally. Since you will get each of those events as the happen and can then update the data entry as it occurs. 

That is the problem with asynchronous interactions.  With our iSync and most likely with A3S from Genesys, there is the need to always reconcile conversations that span over days or even weeks as with Email.  The only possible solution is to only report on conversations that have closed sessions or to automatically close sessions each night.  Also, look at the new aggregate API that came out a couple of weeks ago.

Hi,

The regular analytics API only finds conversations that started during the interval (as to the Jobs endpoint that finds all touched conversations). But the jobs endpoint does not always have the data of yesterday, as it could take 48 hours.

As message conversations can span several days and can start one day and continue another day, that regular endpoint will miss the updated conversations.

Does anyone know of a way to get these incremental updates of yesterday without the need to go back and check all conversations of previous days again, just to see if there's an updated one?

Thanks,

Jeroen

Would using AWS event bridge to get the data instead of using the APIs resolve this naturally. Since you will get each of those events as the happen and can then update the data entry as it occurs. 

That is the problem with asynchronous interactions.  With our iSync and most likely with A3S from Genesys, there is the need to always reconcile conversations that span over days or even weeks as with Email.  The only possible solution is to only report on conversations that have closed sessions or to automatically close sessions each night.  Also, look at the new aggregate API that came out a couple of weeks ago.

Hi,

The regular analytics API only finds conversations that started during the interval (as to the Jobs endpoint that finds all touched conversations). But the jobs endpoint does not always have the data of yesterday, as it could take 48 hours.

As message conversations can span several days and can start one day and continue another day, that regular endpoint will miss the updated conversations.

Does anyone know of a way to get these incremental updates of yesterday without the need to go back and check all conversations of previous days again, just to see if there's an updated one?

Thanks,

Jeroen

That is the problem with asynchronous interactions.  With our iSync and most likely with A3S from Genesys, there is the need to always reconcile conversations that span over days or even weeks as with Email.  The only possible solution is to only report on conversations that have closed sessions or to automatically close sessions each night.  Also, look at the new aggregate API that came out a couple of weeks ago.

Hi,

The regular analytics API only finds conversations that started during the interval (as to the Jobs endpoint that finds all touched conversations). But the jobs endpoint does not always have the data of yesterday, as it could take 48 hours.

As message conversations can span several days and can start one day and continue another day, that regular endpoint will miss the updated conversations.

Does anyone know of a way to get these incremental updates of yesterday without the need to go back and check all conversations of previous days again, just to see if there's an updated one?

Thanks,

Jeroen