New request
#19861: Having issues with real-time updates/SSE
We'll provision a sandbox, run an agent against the issue, and open a draft PR. You can pull the branch and iterate from there.
It's hard to quantify or even really screenshot this issue but this is something I've experienced and other users in my instance.
A lot of the times real-time updates are not working with changes happening that no one else can see until they refresh the page. This is also a case with record deletion and creation, even when deleting a record I have to refresh the page under the Deleted filter to be able to see the deleted record to permanently delete.
To try paint a better picture: Say User 1 is updating multiple fields on a record, once entered even after waiting a couple minutes the updates do not automatically propagate yet if User 1 updates those fields and someone reloads the page i can see the updates.
I can't find a rhyme or reason for it, checking logs shows nothing out of the ordinary when it comes to this or really anything.
This is something that has been happening in my instance since Real-time updates was added to labs a couple versions ago and still affects us now in v1.23.4. This is self-hosted.
Intermittent real-time update failures with no server errors suggest a cross-cutting problem in the SSE/pub-sub pipeline, browser connection lifecycle, or caching layer that requires deep investigation across frontend, backend, and infrastructure.
- packages/twenty-front/src/modules/realtime/hooks/useSSE.ts
- packages/twenty-front/src/modules/apollo/services/apollo.service.ts
- packages/twenty-server/src/engine/subscriptions/subscriptions.module.ts
- packages/twenty-server/src/engine/core-modules/pub-sub/pub-sub.service.ts
- packages/twenty-server/src/engine/core-modules/event-emitter/event-emitter.service.ts
- packages/twenty-server/src/engine/gateway/gateway.module.ts
- docker-compose.yml