DEADLINE_EXCEEDED 🔌 API

gRPC Error: 4 DEADLINE_EXCEEDED: Deadline exceeded

The call didn’t complete before the client’s deadline — slow server, network issues, or a deadline that’s too short.

Seen on: REST API

Meaning

Deadlines propagate across services; a short upstream deadline can expire while downstream services are still working. Cold starts, long database queries and retries also consume time.

Common causes

  • Server or downstream dependency too slow
  • Deadline set too short
  • Network latency/packet loss
  • Server blocked (thread pool exhausted)

⚡ Quick fix

  1. Measure server-side latency; optimise slow paths
  2. Set realistic per-call deadlines
  3. Stream or paginate large responses

Detailed fix by platform

JavaScript

  1. client.getReport({ id }, { deadline: Date.now() + 10_000 }, (err, res) => { /* ... */ });

How to diagnose

  1. Latency — Server-side duration
  2. Deadline — Value used
  3. Chain — Which hop timed out?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.