Poulain_Mathieu | 2018-03-30 08:11:54 UTC | #1
We are working with the notifications on Queue members: v2.routing.queues.{id}.users When a new member is added to the queue we get the following messages:
{ "id": "id...", "queueId": "queue id...", "joined": true, "additionalProperties": {} }
followed by:
{ "id": "id...", "queueId": "queue id...", "joined": false, "additionalProperties": {} }
Looking at metadata the first message has action = update and the second action = add. So if we respect the order the member we added should be joined = false. But in fact he was added with joined = true. Are we doing something wrong, or is it a bug?
rob.gevers | 2018-03-30 17:20:06 UTC | #2
This is essentially a bug. The current event stream takes a single membership change and splits it into multiple events. Currently the 'add' event doesn't reflect the joined status correctly. So you are seeing an add event for any added users, and then an update event for any joined users. I've filed a bug internally to update the setting of the joined flag on the update event. We will also likely provide a newer version of this event contract at some point soon that doesn't provide the redundant updates in this situation. If this is impacting your work and you would like more visibility into the status of the bug, feel free to submit a ticket to our support team, referencing this post.
Poulain_Mathieu | 2018-04-02 06:52:23 UTC | #3
Thank you Rob. I opened a ticket to follow up on this bug.
system | 2018-05-03 06:59:18 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 2684