Since the latest update in February 2025 of the Genesys Connector, the endpoint being used was changed to better retrieve the "Historical" data out of Genesys. BUT the issue is that the endpoint now being used is pulling from Genesys' Data Lake and thus is only updated once per day in the middle of the night. So no conversation data is coming over for today's call and conversation activity.   This creates a difficult decision with this connector on whether to favor historical data vs recent up-to-date data. 

My recommendation is to leave the connector as is in getting the conversation_analytics_details but then also grab and update the "recent" records using the /api/v2/conversations/{conversationId} endpoint and put those values for maybe the past 48 hours into a separate set of tables in the destination database.. Then we can join these data into our reports or data pipelines if we wish downstream in the destination database. 

I understand that you're put in a position with this API to choose one vs the other API endpoint but I'd say, why not offer both and allow the customers to "un-select" some of those tables if they don't want to sync all of it?