Error with Omnichannel + WhatsApp(Twilio) After upgrade 3.10.5

Community Support
1

Description

After upgrading from 3.9.3 to 3.10.5 a weird error is occurring in the omnichannel. Somehow the messages of a WhatsApp session arrive broken, that is, when the user from WhatsApp sends a text to the RC, the message session arrives in parts and is assigned to different omnichanel agents.
for example:
WhatsApp user sends
Text1: Hello
Text 2: I have a problem
Text3: with the O365 password
In the RC are assigned:
Agent1: Hello
Agent2: I have a problem
Agent 3: with O365 password

I have tried to do a downgrade with snap revert, but without success since when performing the process, it does not start the RC (I assume that there must be some change in the DB that prevents the return)
Any ideas?

Server Setup Information

  • Version of Rocket.Chat Server: 3.10.5
  • Operating System: Ubuntu LTS 18.04 AWS
  • Deployment Method: Snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: v12.18.4
  • MongoDB Version: 3.6.14
  • Proxy: nginx
  • Firewalls involved:

Any additional Information

Provider: Twilio + WhatsApp Bussines API

2

Here I had a similar problem. I need to keep version 3.9.3 of Rocket.chat. After that, images received via Twilio are not displayed. A link appears that leads to a page not found (Error 404).

Did you solve your problem?

3

Not yet :frowning: still persist in 3.12