[CW-1957] Web app disconnects and doesn't notify about incoming messages anymore

[mariusa]

Describe the bug

Using https://app.chatwoot.com/app/

To Reproduce
No steps, sorry, it happens sometimes while leaving the browser tab open and not visiting it, including after browser restart.

When visiting it, the page renders and there's a Chatwoot message at top-right "Disconnected from Chatwoot" and a link to Refresh.

Expected behavior

Instead of showing the "Disconnected" message, auto-refresh / connect again.
If offline after 3 tries, continue trying every 1 minute to connect again.

Environment

Describe whether you are using Chatwoot Cloud (app.chatwoot.com) or a self-hosted installation of Chatwoot. If you are using a self-hosted installation of Chatwoot, describe the type of deployment (Docker/Linux VM installation/Heroku/Kubernetes/Other).

• app.chatwoot.com (Chatwoot Cloud)
• Self-hosted
• • Linux VM
• • Docker
• • Kubernetes
• • Heroku
• • Other (Please specify)

Desktop (please complete the following information) (If applicable)

• OS: Linux
• Browser Chrome
• Version 1098

_CW-1957

[arladmin]

I keep experiencing this, on both, Chatwoot cloud app as well Self-hosted one.

[arladmin]

@pranavrajs
@muhsin-k

Is there any fix/workaround for this, so far?

Without a fix, it actually doesn't make much sense to continue using Chatwoot for various types of inboxes, eg. Whatsapp, Website, and others, where an incoming message is expected to pop-up/create a notification, immediately upon its arrival, and not wait for the user to navigate to the app!

[tyler-wright]

Surprised this one is marked as low priority, it actually significantly reduces the usefulness particularly of the mobile app which you would expect to notify you in the background like many other apps when a chat comes through.

[linear]

CW-1957 Web app disconnects and doesn't notify about incoming messages anymore

[pranavrajs]

This configuration would allow you to automatically resolve the conversation after a specific time period. Configure the time frame and personalized message to the user below.

When a disconnect occurs, the web-socket events intended for the UI are discarded and lost.

• Caches are present for Agents, Labels, Inboxes, and Teams. We need to verify whether these caches have been invalidated. If they have, we should use the APIs to refetch the models. This logic already exists in account.cache_invalidated.
• For the currently active conversation, fetch the messages were added / updated after the disconnection time.
• Retrieve the conversations that were updated after the disconnection time based on the active filters in the UI.