Skip to content

Client: Add HTTP fallback for lease extensions - #1403

Draft
lucas-felicity wants to merge 1 commit into
inngest:mainfrom
felicity-ai:fix/connect-lease-http-fallback
Draft

Client: Add HTTP fallback for lease extensions#1403
lucas-felicity wants to merge 1 commit into
inngest:mainfrom
felicity-ai:fix/connect-lease-http-fallback

Conversation

@lucas-felicity

Copy link
Copy Markdown

No description provided.

When the WebSocket is unavailable (e.g., during gateway drain or
reconnection), lease extensions were silently dropped with just a
warning log. After 25 seconds without extension, the server returns
connect_worker_stopped_responding even though the step is still running.

This adds an HTTP fallback: when the WebSocket is not OPEN, the SDK
POSTs the lease extension directly to the API server at
/v0/connect/extend-lease, bypassing the gateway entirely. The API
server extends the lease in the shared Redis state.

The HTTP path is only active during the reconnection gap. Once a new
WebSocket is established, lease extensions go back to the normal
WebSocket path.

Companion server change: inngest/inngest

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lucas-felicity lucas-felicity changed the title Client: Add HTTP fallback for lease extensions during gateway drain Client: Add HTTP fallback for lease extensions Mar 24, 2026
@changeset-bot

changeset-bot Bot commented Mar 24, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 1f147ce

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant