Cursor realtime

Server-Sent Events Disconnecting in Cursor Application

Your Cursor-generated application uses Server-Sent Events (SSE) for real-time updates (live notifications, streaming responses, dashboards), but the SSE connection drops after a few seconds or minutes. Users see the real-time feed freeze, and the browser's EventSource silently reconnects only to disconnect again in a loop.

SSE connections are long-lived HTTP connections that must stay open indefinitely. This conflicts with many infrastructure components that expect short request-response cycles. Reverse proxies, load balancers, serverless platforms, and CDNs all have default timeouts that terminate SSE connections prematurely.

The issue is often intermittent — it works fine during development where there's no proxy layer, but fails in production where Nginx, Cloudflare, or a serverless platform sits between the client and server.

Error Messages You Might See

EventSource failed: net::ERR_INCOMPLETE_CHUNKED_ENCODING EventSource connection lost, reconnecting... 504 Gateway Timeout Error: stream timeout after 60000ms ReadableStream has been disturbed or locked
EventSource failed: net::ERR_INCOMPLETE_CHUNKED_ENCODINGEventSource connection lost, reconnecting...504 Gateway TimeoutError: stream timeout after 60000msReadableStream has been disturbed or locked

Common Causes

  • Reverse proxy timeout — Nginx, Apache, or Cloudflare terminates idle connections after 60-120 seconds by default
  • Serverless function timeout — Vercel (30s), Netlify (26s), and Lambda (15min max) kill long-running functions, terminating the SSE stream
  • No keep-alive heartbeat — Without periodic data sent on the connection, intermediaries assume it's dead and close it
  • Missing SSE headers — The response lacks required headers like Content-Type: text/event-stream, Cache-Control: no-cache, or Connection: keep-alive
  • Response buffering enabled — Nginx or Node.js response compression buffers SSE data instead of streaming it, causing events to arrive in batches or not at all

How to Fix It

  1. Send heartbeat comments every 15-30 seconds — Send SSE comment lines (: heartbeat\n\n) at regular intervals to keep the connection alive through proxies and load balancers
  2. Configure proxy timeouts — For Nginx: set proxy_read_timeout 86400s; and proxy_buffering off;. For Cloudflare: enable WebSockets/SSE in the dashboard or use Cloudflare Tunnel
  3. Disable response buffering — Add X-Accel-Buffering: no header for Nginx, and disable compression on SSE endpoints
  4. Implement robust client reconnection — Use EventSource's built-in reconnection with a custom retry: field, and include Last-Event-ID handling to resume from where the client left off
  5. Avoid serverless for SSE — If your SSE needs long-lived connections, deploy on a traditional server (VPS, container) rather than serverless functions. Alternatively, use a managed service like Ably or Pusher
  6. Set correct response headers — Ensure every SSE endpoint sends: Content-Type: text/event-stream, Cache-Control: no-cache, Connection: keep-alive

Real developers can help you.

Vlad Temian Vlad Temian 15+ years shipping production infrastructure for startups. Former CTO at qed.builders (acquired by The Sandbox). Cursor ambassador and agentic tooling builder. I've scaled systems, automated deployments, and built observability tools for AI coding workflows. I specialize in taking vibe-coded apps from broken prototype to production-ready: fixing Supabase auth/RLS, Stripe integrations, deployment pipelines, and cleaning up AI-generated spaghetti. I build tools in this space (agentprobe, claudebin, micode) and understand both sides: how AI generates code and why it breaks. https://blog.vtemian.com/ MFox MFox Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking. prajwalfullstack prajwalfullstack Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help Jared Hasson Jared Hasson Full time lead founding dev at a cyber security saas startup, with 10 yoe and a bachelor's in CS. Building & debugging software products is what I've spent my time on for forever Basel Issmail Basel Issmail ’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems. My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale. In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals. I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software. Matthew Butler Matthew Butler Systems Development Engineer @ Amazon Web Services Omar Faruk Omar Faruk As a Product Engineer at Klasio, I contributed to end-to-end product development, focusing on scalability, performance, and user experience. My work spanned building and refining core features, developing dynamic website templates, integrating secure and reliable payment gateways, and optimizing the overall system architecture. I played a key role in creating a scalable and maintainable platform to support educators and learners globally. I'm enthusiastic about embracing new challenges and making meaningful contributions. Jacek Rozanski Jacek Rozanski Senior PHP/Symfony developer and DevOps engineer with 20+ years of professional experience, running opcode.pl (web development agency, est. 2004). Day job: I'm the sole backend developer at merketing company where I own and maintain 11 PHP/Symfony microservices on AWS (ECS Fargate, RDS, S3, CloudFront), handle the full CI/CD pipeline (Bitbucket Pipelines, Docker), and manage monitoring with Sentry and CloudWatch. These services handle high request volumes in production every month. What I bring to AI-built apps: - I audit and fix security issues (OWASP methodology), performance bottlenecks, and architectural problems in codebases generated by Cursor, Claude Code, Lovable, Bolt, and v0 - I refactor AI-generated prototypes into production-grade applications with proper error handling, testing, and clean architecture (SOLID, DDD, hexagonal architecture) - I set up the infrastructure AI tools don't touch: AWS hosting, CI/CD pipelines, automated deployments, database optimization, monitoring, and alerting - I integrate external services: payment providers, email systems, partner APIs, SSO/auth Tech stack: PHP 8.x, Symfony, React, Next.js, PostgreSQL, MySQL, Docker, AWS (ECS, RDS, S3, SQS/SNS, CloudFront), Terraform, Supabase. I also use AI tools daily (Claude Code, Cursor) in my own workflow, so I understand both the strengths and the gaps in AI-generated code. Based in Poland (CET timezone). Available for async work and calls during EU/US business hours. Krishna Sai Kuncha Krishna Sai Kuncha Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : ) Alvin Voo Alvin Voo I’ve watched the tech landscape evolve over the last decade—from the structured days of Java Server Pages to the current "wild west" of Agentic-driven development. While AI can "vibe" a frontend into existence, I specialize in the architecture that keeps it from collapsing. My expertise lies in the critical backend infrastructure: the parts that must be fast, secure, and scalable. I thrive on high-pressure environments, such as when I had only three weeks to architect and launch an Ethereum redemption system with minimal prior crypto knowledge, turning it into a major revenue stream. What I bring to your project: Forensic Debugging: I don't just "patch" bugs; I use tools like Datadog and Explain Analyzers to map out bottlenecks and resolve root causes—like significantly reducing memory usage by optimizing complex DB joins. Full-Stack Context: Deep experience in Node.js and React, ensuring backends play perfectly with mobile and web teams. Sanity in the Age of AI: I bridge the gap between "best practices" and modern speed, ensuring your project isn't just built fast, but built to last.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

Can I use SSE with serverless platforms like Vercel?

Standard SSE with long-lived connections doesn't work well with serverless platforms due to function execution time limits. Vercel supports streaming responses for up to 30 seconds. For longer connections, use a dedicated WebSocket service (Ably, Pusher, Supabase Realtime) or deploy the SSE endpoint on a traditional server.

How is SSE different from WebSockets?

SSE is unidirectional (server to client only), uses standard HTTP, and has built-in reconnection. WebSockets are bidirectional, use a separate protocol (ws://), and require manual reconnection logic. Use SSE when you only need server-to-client updates; use WebSockets when you need two-way communication.

Related Cursor Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help