Hi @Donovan Teixeira de Lima
We've experienced similar issues in our organisation.
There can be several causes behind this behaviour. For example, a service disruption (such as an AWS-related issue) or certain abnormal flow or routing conditions can leave an interaction in an inconsistent state between the Conversations and Analytics services. In these situations, the conversation may have already ended, but Analytics might not update the interaction timeline correctly.
This would align with the symptoms you're describing:
- The interaction remains visible against the agent or queue for several days.
- It does not appear under Active Interactions.
- The interaction details indicate that it actually ended earlier.
As an initial troubleshooting step, try forcing the disconnect again from Admin > Routing > Disconnect Interactions. as Suggested by @Charles-Henri Vannimenus.
However, if the interaction has already ended at the Conversations service level, the disconnect operation may not remove the stale Analytics entry. We've encountered cases where a force disconnects did not resolve the issue.
If the problem persists, I recommend opening a Genesys Cloud Support case and providing the affected conversation IDs. Support can review the backend logs and interaction state and, if necessary, use internal tools to resynchronise or clear the stuck interactions.
Hope this helps.
------------------------------
Akhil
------------------------------