Understand how our platform uses Server-Sent Events (SSE) to push data directly to a user's browser in real time. Learn why network security tools sometimes flag and block SSE connections.
Required Editions
| User Permissions | |
|---|---|
| To manage connections and handle messaging sessions: |
|
| To reply or transfer conversations: | Access Conversation Entries permission. This permission is available via the Service Cloud Voice User license or the Agentforce Service Agent User license. |
Unlike traditional polling, where a browser constantly asks for updates, SSE keeps a single open line for instant delivery.
| Feature | polling | SSE |
|---|---|---|
| Connection | Short-lived, frequent | Long-lived, single connection |
| Efficiency | Low (high overhead) | High (low overhead) |
| Latency | Delayed | Instant (real-time) |
Why Network Security Blocks SSE
Because SSE connections stay open indefinitely, security tools designed for stop-and-start web traffic often flag them. Common failure points include:
- SSL and TLS inspection: Security engines sometimes buffer the stream to scan for viruses. Because the stream never ends, the data is held indefinitely and never reaches the user.
- Proxy buffering: Proxies waiting for a full file never see one, which causes the application to freeze.
- Connection timeouts: Firewalls sometimes kill the connection if they deem it idle during quiet periods.
- Configure Your Network for Server-Sent Events
Make sure that your real-time messaging services have stable connectivity by configuring your IT and network security settings.