PureEngage On-Premises

 View Only

Sign Up

  • 1.  Stuck interactions showing for days in queue, but not listed as active interactions

    Posted 02-13-2026 13:54
      |   view attached

    Hello everyone,

    I'm seeing an odd behavior in my Genesys Cloud queues and agent activity view.

    Some agents are displayed as having interactions lasting 4 or even 6 days in a specific queue. However:

    • These interactions do not appear in the "Active Interactions" list.

    • When I open interaction details, they show as already ended a long time ago.

    • I tried copying the interaction ID and using manual disconnect, but nothing changes.

    • The interactions remain visible in the queue/agent view.

    Eventually, after some time (hours or days), they usually disappear by themselves.

    My questions:

    • What causes these stuck/ghost interactions?

    • Is this related to a sync issue, cache, or backend processing delay?

    • Is there any recommended action to force refresh or clean these interactions?

    This behavior is impacting real-time monitoring and queue visibility.

    Thanks in advance for any guidance.


    #Platform/SystemAdministration

    ------------------------------
    Donovan Teixeira
    ------------------------------


  • 2.  RE: Stuck interactions showing for days in queue, but not listed as active interactions

    Posted 09-29-2026 09:25

    Hello,
    It happens once after an AWS issue
    You can try to force the disconnection again using the directory/#/admin/routing/disconnectInteractions route
    If nothing works, just create a case on Genesys Support and they are able to sync those stuck interactions for you



    ------------------------------
    Charles-Henri
    Consultant Customer eXperience
    ------------------------------



  • 3.  RE: Stuck interactions showing for days in queue, but not listed as active interactions

    Posted 09-29-2026 09:46

    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
    ------------------------------