From 95c2cbfcb3f75fb51eca096ebf12370555f03f2f Mon Sep 17 00:00:00 2001 From: Simon Woolf Date: Tue, 30 Jun 2026 12:02:38 +0100 Subject: [PATCH] errors: add 80025 for exceeded max concurrent connections per token MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The realtime platform enforces (or, in monitor mode, measures) a limit on the number of concurrent connections sharing a single auth token. There was no error code for this case; the existing nodejs implementation reused 80019, which actually means "client configured authentication provider request failed" — an unrelated, client-side auth error that SDKs may react to by retrying auth. Add a dedicated connection-range code so the rejection is described accurately. Co-Authored-By: Claude Opus 4.8 (1M context) --- protocol/errors.json | 1 + 1 file changed, 1 insertion(+) diff --git a/protocol/errors.json b/protocol/errors.json index 3c432ec9..4b21e846 100644 --- a/protocol/errors.json +++ b/protocol/errors.json @@ -181,6 +181,7 @@ "80022": "unable to continue current comet connection", "80023": "unable to resume connection from a different site", "80024": "protocol version is no longer supported", + "80025": "exceeded maximum concurrent connections permitted for this token", "80030": "client restriction not satisfied", "90000": "channel operation failed",