Weird notification on "v2.routing.queues.{id}.users" topic

I have a situation that is causing me some problems because of some intermittently missing notifications.

I have a queue which has a group added to it. Membership in the queue is managed by adding and removing users from the group. I've subscribed to the "v2.routing.queues.{id}.users" topic for this queue so I will receive notifications when users join or leave the queue.

What I see when I test this in the dev tools is that when I add a user to the group, I will receive two notifications that look like this:

 {
  "id": "{userid}",
  "user": {
    "id": "{userid}"
  },
  "queueId": "{queueid}",
  "additionalProperties": {}
}
 {
  "id": "{userid}",
  "user": {
    "id": "{userid}"
  },
  "queueId": "{queueid}",
  "joined": true,
  "additionalProperties": {}
}

Notice one of them has the "joined" attribute, and one of them doesn't.

When I remove the user from the group, I will sometimes get both notifications, but sometimes I will only get the one that doesn't include the "joined" attribute. With that, the notification doesn't tell me if the user has joined or left. This is intermittent. Earlier today I was reliably missing the notification that included the "joined" attribute. While testing just now, I'm seeing both notifications come through and I am unable to reproduce the issue.

I will continue testing this to see if I can reproduce the issue again and capture the Correlation IDs of the notifications.

This is causing a problem for us because we are trying to have data in our database match what Genesys Cloud shows as far as queue membership. I need to know when users are added to or removed from a queue.

UPDATE:
I was able to reproduce the issue. I did the same process as before: Added a user to a group (received two notifications), removed the user from the group and only received one notification. The one notification I got on the remove did not include the "joined" property. The correlation ID for the two notifications from the successful add is "a6db3863-1968-45f5-80db-af0f8a350b16". The correlation ID from the single remove notification is "ed7de3ff-a007-47e7-9b7b-9f4c803a8944".

Keep in mind that WebSockets, by definition of the protocol itself, does not guarantee message delivery. If you need guaranteed delivery to ensure integrity of your data, you need to use the EventBridge integration. You didn't mention which you're using, but wanted to point out this distinction to make sure you're using an appropriate transport type for your use case.

Regardless of transport type, if you believe you are missing data or events please open a case with Genesys Cloud Care to investigate. We do not have access to your org's data to be able to perform missing data investigations via the forum.

Thanks for the response, Tim.

We're using WebSockets in our application, but I'm not sure what's being used in the Genesys Developer Tools when testing notification subscriptions. We're seeing missing events in both environments.

We'll open a case with Genesys Cloud Care and have them investigate to see if they have any additional insight into it.

Thanks again!

FWIW that's websockets also.

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