Genesys Cloud - Main

 View Only

Sign Up

  • 1.  User Presence Issue

    Posted 3 hours ago

    Since 07/08/2026, we have been experiencing issues with a group of users that cannot change their status in the Genesys UI.  When the users try to change their own status, they get an error message " Error Setting Presence".  When a supervisor or admin tries to change the user's status, the status immediately reverts to the stuck status. In both cases, there is a 409 error in the network logs to the /api/v2/users/{userId}/presences/purecloud api.

    We have a support case open and provided logs but they are focusing on "net::ERR_CONNECTION_RESET" for requests to https://ca.az.contentsquare.net/ which we have always blocked and for https://127.0.0.1:8191/gcbaId which is for Screen Recording which we don't use. 

    Are other customers experiencing issues with User Presence since last week?  The issue seems to be on the Genesys side and not related to any network connectivity, but we are struggling to get Genesys Support to dig into this issue.


    #API/Integrations
    #System/PlatformAdministration
    #WEM-Quality,WFM,Gamification,etc

    ------------------------------
    Russell Clark
    Software Engineer - I/T
    ------------------------------


  • 2.  RE: User Presence Issue

    Posted 2 hours ago
    Based on what you've described, I agree that the 409 Conflict response on the /api/v2/users/{userId}/presences/purecloud endpoint seems to be the key point to investigate. The contentsquare and gcba errors don't appear to explain why the presence update itself is being rejected, especially if they have always been present in your environment.
     
    Since you already have a Customer Care case open, I'd recommend requesting an escalation to the team responsible for Presence so they can troubleshoot the issue together with you. The exact reason for the conflict should be visible on the backend.
     
    As an additional check, I'd verify whether the affected users have anything in common, such as the same integration controlling presence (if any), the same division, role, or routing configuration, and whether the issue affects only existing users or can also be reproduced with a newly created test user.


    ------------------------------
    Raphael Poliesi
    ------------------------------



Related Content