Skip to content

Data Streams WebSocket: document 1000 close code - #4423

Merged
dev-dist merged 5 commits into
smartcontractkit:mainfrom
sebastian-lerner-link:data-streams-ws-close-codes
Nov 12, 2026
Merged

dev-dist merged 5 commits into
smartcontractkit:mainfrom
sebastian-lerner-link:data-streams-ws-close-codes

Conversation

@sebastian-lerner-link

@sebastian-lerner-link sebastian-lerner-link commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds a short Connection closures section to the Data Streams WebSocket API reference. It says the server always sends close code 1000 when it closes a connection, including during deployments and failover, and that clients should reconnect.

Customers have asked whether repeated 1000 closes indicate a problem; this makes the expected behavior explicit. No server behavior changes.

🤖 Generated with Claude Code

Explain that the server sends close code 1000 for all server-initiated
closures (including restarts and failover) and that clients should
always reconnect, with RFC 6455-aligned backoff guidance.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 10, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Chainlink Labs Team on Vercel.

A member of the Team first needs to authorize it.

Sebastian Lerner and others added 2 commits November 10, 2026 14:30
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sebastian-lerner-link sebastian-lerner-link changed the title Data Streams WebSocket: document connection closures and reconnecting Data Streams WebSocket: document 1000 close code Nov 10, 2026
@dev-dist
dev-dist enabled auto-merge (squash) November 12, 2026 00:32
@dev-dist
dev-dist merged commit 0401189 into smartcontractkit:main Nov 12, 2026
12 of 14 checks passed
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.

2 participants