Skip to content

errors: add 80025 for exceeded max concurrent connections per token#347

Open
SimonWoolf wants to merge 1 commit into
mainfrom
add-error-80025-max-token-connections
Open

errors: add 80025 for exceeded max concurrent connections per token#347
SimonWoolf wants to merge 1 commit into
mainfrom
add-error-80025-max-token-connections

Conversation

@SimonWoolf

Copy link
Copy Markdown
Member

Summary

  • Adds error code 80025: "exceeded maximum concurrent connections permitted for this token".

Why

The realtime platform measures (and can enforce) a limit on the number of concurrent connections sharing a single auth token. There was no dedicated error code for this case.

The existing nodejs implementation (common/lib/security/authparams.ts) reuses 80019 for it — but 80019 actually means "client configured authentication provider request failed", an unrelated client-side auth error that SDKs may react to by retrying authentication. Surfacing it for a server-side concurrency limit is misleading.

80025 is the next free code in the contiguous connection-error block (800xx). Once this merges, the realtime repo will switch the nodejs check to 80025 and the in-progress Go frontdoor implementation (PUB-1503) will use it too.

No errorsHelp.json entry is added, as no FAQ article exists for this code yet.

🤖 Generated with Claude Code

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) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant