Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 25 additions & 14 deletions docs/core-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -796,20 +796,31 @@ reuse that discovery to stop a seat.
CloudMatch instead of treating the first empty regional response as authoritative.
Discovery deduplicates session IDs and uses at most four concurrent requests, a
three-second per-request timeout, a 12-second total budget (including region
discovery), and at most 32 regional endpoints. If no sessions were found but a
region failed, returned invalid data, or could not be checked within these bounds,
the request fails with `session_discovery_failed` rather than returning an empty
list. HTTP 401 remains `http_unauthorized` after at most one safe-read renewal;
HTTP 403 remains `authentication_required`. A found session
can be returned even when another region fails; an empty successful list means
all discovered regions were checked successfully. Reconnect, reconciliation, and
known-conflict discovery remain strict: callers must not treat a discovery failure
as proof that an existing session has ended. For a current new-launch intent with
no active or known conflicting session, Qt may revalidate the selected game and
attempt `session.create` after `session_discovery_failed`. CloudMatch's
`session_conflict` response still redirects that attempt to resume/end handling;
discovery failures after a known conflict never trigger another create. Authentication
errors, cancellation, and request timeouts do not use this fallback.
discovery), and at most 32 regional endpoints. While no session has been found and
no region rejected the credentials, a region or region-discovery request that failed
transiently is retried once with a 1.5-second timeout. A fast failure is retried 750
ms later, and a timeout, which has already waited three seconds, at once. The retry
runs only if more than the delay plus 1.5 seconds of the budget remain, so a region
that keeps timing out fails the sweep after about 4.5 seconds. Transient means HTTP
408, 425, 429, 500, 502, 503, or 504 (the statuses session polling retries) or a
transport failure such as a timeout or a closed connection; other HTTP statuses,
invalid bodies, and rejected `requestStatus` values are final. If no sessions were
found but a region failed, returned invalid data, or could not be checked within
these bounds, even after that retry, the request fails with
`session_discovery_failed` rather than returning an empty list. HTTP 401 remains
`http_unauthorized` after at most one safe-read renewal; HTTP 403 remains
`authentication_required`. A found session can be returned even when another region
fails; an empty successful list means all discovered regions were checked
successfully. Reconnect, reconciliation, and known-conflict discovery remain strict:
callers must not treat a discovery failure as proof that an existing session has
ended. For a current new-launch intent with no active or known conflicting session,
Qt may revalidate the selected game and attempt `session.create` after
`session_discovery_failed`. CloudMatch's `session_conflict` response still redirects
that attempt to resume/end handling; discovery failures after a known conflict never
trigger another create. Authentication errors, cancellation, and request timeouts do
not use this fallback. Each sweep records one bounded `[session] discovery:`
diagnostics line with each failed request's kind and attempt number, naming regions
by CloudMatch metadata key, never by URL.

### Provider routing and account scope

Expand Down
Loading