[FIX] Omnichannel Inquiry queues when removing chats #16603
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We detected some issues related to the Omnichannel Inquiries when removing chats:
streaming
was relying on therid
field, but when removing aninquiry
, only the_id
is propagated, so it wasn't working properly.inquiry
was not being removed in some events when theroom
was removed, so theinquiry
was becoming available even without the existence of the relatedroom
.Some customers have experienced issues related to this case, as shown below: