# rpc error: code = DeadlineExceeded desc = context deadline exceeded

- **ID:** `go/grpc-deadline-exceeded-server`
- **Domain:** go
- **Category:** runtime_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

The client-side context deadline elapsed before the server responded; the server may still be processing, or the network is slow.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| google.golang.org/grpc 1.40+ | active | — | — |

## Workarounds

1. **** (90% success)
   ```
   Propagate deadlines from the caller and add per-RPC timeout at the client:
ctx, cancel := context.WithTimeout(ctx, 2*time.Second)
defer cancel()
resp, err := client.Get(ctx, req)
   ```
2. **** (85% success)
   ```
   Instrument server-side handler duration (otelgrpc / prometheus) to distinguish slow processing from network latency, then tune deadline accordingly.
   ```

## Dead Ends

- **** — Removes the safety net; hung servers block callers forever and exhaust connection pools. (70% fail)
- **** — Without jitter/backoff, retries amplify load on an already-slow server, causing cascading timeouts. (75% fail)