Closed yacjne closed 1 month ago
Engineer dispatched. See details on the Maige dashboard. | Name | Status | Message | Updated (UTC) |
---|---|---|---|---|
Fix Real-time Message Display in Raven | 🟡 Pending (inspect) | May 13, 2024, 11:42 AM |
Hi @yacjne - is this issue with the Raven web app or the Desk integration? Can you check if the websocket events are being received?
It looks like the issue is with the Raven web/mobile app. websocket events are not being sent or received.
Also, when testing the Desk integration, I encountered a permission error despite having full permissions on my user (not Administrator).
(api/method/raven.api.raven_users.get_list 403 (FORBIDDEN))
It's possible that your socket events aren't working on your site. Is this self hosted or on Frappe Cloud?
It's self hosted and running on two different environments
Can you check if your socket connection is receiving any event? To do this, open the browser dev tools, refresh the page and check the network tab. See if the "ws" connection is being established or not.
My hunch is that your websocket connection is not being established or is being closed automatically probably because of a configuration in your Procfile. You can also check the status of the processes in supervisor on your server.
Socket events are not being sent or received, although they are working fine in another bench.
The socket connection is established, but when we send a message, the status remains stuck on "Pending."
We will investigate this issue further.
Thank you for your help :)
@yacjne we are experiencing the same issue. did you ever find a solution ?
Hello @RJPvT,
Unfortunately, we haven't resolved the issue yet. It works on some instances but not on others, and we haven't figured out the cause. We'll update you with any solutions we find.
@yacjne Can you come on a call for me to look at the issue? Also, you can use https://community.ravenapp.cloud
Hello,
We are experiencing an issue in our production environment where sent and received messages are not displaying in real-time, requiring a page refresh.
The socket connection appears to be functional without any errors logged in the console.
Could anyone suggest potential solutions to resolve this issue?
Thank you!