Mismatch in user queues between API and Websocket

Hi,

We made an realtime user activity overview based on websockets. We subscribe to the v2.users.{id}.activity events to process changes in the activity and the queues. However, on some users we get more queues in the activeQueueIds object in the websocket message body than the user is member of. If I make an API call to get the queues of that member, or check in the Genesys GUI, there are (in the examples i got) less active queues for the user than in the websocket message.

Is there an logical explanation for this or could this be a bug?

Regards,
Dennis

Hi Dennis,

There is no logical reason that there should be a difference. Please open a case with Genesys Customer Care regarding this issue.

1 Like

FYI; The issue was identified and the Genesys developers are now working on a resolution.

@DennisCC what is the response from the genesys could you explain

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.