fix: keep runtime alive during channel recovery - #25
Draft
tylerslaton wants to merge 1 commit into
Draft
Conversation
AlemTuzlak
added a commit
to CopilotKit/CopilotKit
that referenced
this pull request
Aug 4, 2026
## What changed - Mark initial gateway HTTP 5xx and transient transport failures as retryable. - Retry initial managed Channel activation with exponential backoff from 1 second to a 30-second cap until it connects or the manager stops. - Preserve retry hints from `gateway_draining` join replies and retry initial join timeouts. - Keep HTTP 4xx and NXDOMAIN failures terminal. - Back off established-session outage reminders from 30 seconds to a 15-minute cap while Phoenix continues reconnecting. ## Why The OpenTag Railway runtime saw the gateway host return HTTP 502 during an outage. Established Phoenix sessions keep retrying, but a runtime that starts during the outage stops after its one initial connect window. It cannot recover when the gateway comes back unless the process restarts. Fixed 30-second reminder logs also flood long outages. The gateway drain work now rejects new joins with a structured retryable response. The client must preserve that response so the runtime can retry instead of leaving the Channel in a terminal error state. ## Companion change CopilotKit/OpenTag#25 keeps the Railway HTTP server alive while an initial Channel retry is pending. OpenTag must consume a CopilotKit release containing this PR before that companion change can recover by itself. ## Validation - `pnpm nx run-many -t test,check-types,build -p @copilotkit/runtime,@copilotkit/channels-intelligence` - `pnpm nx run-many -t publint,attw -p @copilotkit/runtime,@copilotkit/channels-intelligence` - pre-commit tests and package checks for all affected projects - `pnpm exec oxfmt --check` on all five changed files - `pnpm exec oxlint` on all five changed files - `git diff --check`
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
A runtime that starts during a realtime gateway outage currently exits before a retry can connect after the gateway recovers. Keeping the HTTP health route alive lets the CopilotKit retry loop eventually restore the managed Channel without a process restart.
Dependency
Depends on CopilotKit/CopilotKit#6347 and a CopilotKit release that includes it. That change retries transient initial gateway activation with exponential backoff.
Validation
pnpm exec vitest run app/server-recovery.test.ts app/server.test.ts --reporter=verbose— 6 tests passedgit diff --checkExisting repository failures
pnpm check-typesfails unchanged on the clean base checkout because@copilotkit/channels0.6.1 and the runtime transitivechannels-core0.6.0 expose incompatible types.