A venue read whose connection drops is sent once more
Market detail, events and the other routes that read a venue when you call them no longer answer 502 when the connection to the venue ends before it answers; the read is sent again.
GET /v1/markets/{market_id}, GET /v1/events/{event_id}, crypto prices and the Polymarket wallet routes read the venue when you call them. A read whose connection to the venue ended before any answer failed the request with 502 upstream_unavailable, even with the venue up: on November 11 a market detail lookup of a Predict market failed this way 14 milliseconds in. Now such a read is sent once more, on a fresh connection, and the request answers as usual. A read is sent at most twice and only when nothing came back: an answer from the venue, an error status included, is never sent again, and neither is a read that ran out of time. A 502 still means the venue did not answer, and retrying later is still right. No field or parameter changed.