timeouts client Shipped
What this lens looks for
Every request must set both a connection timeout and a read timeout — infinite timeouts must never be used: a connection timeout (TCP + TLS handshake, default 10 seconds), a read/response timeout (time to first byte, default 30 seconds), and a total/request timeout covering the entire lifecycle including retries (default 60–120 seconds); for long-running operations, do not extend timeouts to accommodate them — use the 202 Accepted plus polling pattern instead.
What its verifier checks
Each network request sets a connection timeout (≈10s) and a read/response timeout (≈30s), with a total/request-lifecycle timeout (≈60–120s) bounding retries; no request is left with an infinite or unset timeout (e.g., a fetch() with no AbortController or equivalent); long-running operations use a 202 Accepted plus polling pattern rather than an extended timeout.