fix(world-vercel): resume an in-flight step_started after a lost WebSocket connection by shalabhc · Pull Request #4502 · vercel/workflow

shalabhc · 2026-09-30T01:16:51Z

Makes the WebSocket events transport survive a connection that is lost while a step_started write is in flight.

Problem

step_started can't be retried as a new write: a second start counts as another step attempt. So a WebSocket closing between sending a step_started and receiving its reply fails the step's delivery. The queue redelivers it, and every redelivery spends a step attempt.

Change

step_started requests are now resumable:

Negotiation. The upgrade request offers x-workflow-ws-features: resumable-step-started. A server that supports it answers with a features frame right after the upgrade. Servers that don't support it ignore the header and never send the frame.
Lost connection. If the connection is lost before the reply arrives, a resumable request isn't failed. The transport reconnects (the existing eager reconnect) and waits up to 2 s for the new connection's features frame.
Resend. If the new connection supports the feature, the request is resent byte-identical to the original apart from its per-connection reqId, with retransmit: true. The frame is rebuilt from the same input, so it carries the same client-stamped occurredAt and ownerMessageId. The server uses those to recognise a write it already applied and answers from its record instead of applying it again. The reply may carry replayed: true.
Fallback. Otherwise, and when the reconnect budget runs out, the channel is released, or the request's deadline passes (still measured from the first send), the request fails exactly as before.

Other event types are unchanged: they keep failing on a lost connection and are re-sent by event-retry.ts as today.

Telemetry: the client span gets workflow.events.ws.retransmitted and workflow.events.ws.replayed.

Tests

ws-transport.test.ts:
- the feature is offered on every upgrade;
- a lost resumable request is resent on the next connection with retransmit: true and a new reqId, and resolves with that reply;
- it fails with the original close error when the new connection never announces the feature;
- non-resumable requests still fail on close;
- releasing the channel fails a request waiting to be resent;
- one deadline covers the whole request, including the resend.
events-v4-ws.test.ts:
- step_started is sent as resumable and other types aren't;
- a resend differs from the original only in reqId and retransmit.
Checks: pnpm typecheck and vitest run src for @workflow/world-vercel pass (790 tests).

…ocket connection Co-Authored-By: Shalabh Chaturvedi <7066873+shalabhc@users.noreply.github.com>

vercel · 2026-09-30T01:17:00Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
example-nextjs-workflow-turbopack	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
example-nextjs-workflow-webpack	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
example-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-astro-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-express-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-fastify-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-hono-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-nestjs-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-nitro-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-nuxt-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-python-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-sveltekit-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-tanstack-start-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workbench-vite-workflow	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workflow-docs	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workflow-swc-playground	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workflow-tarballs	Ready	Preview, v0	Sep 30, 2026 1:20am UTC
workflow-web	Ready	Preview, v0	Sep 30, 2026 1:20am UTC

changeset-bot · 2026-09-30T01:17:02Z

🦋 Changeset detected

Latest commit: 854f136

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 17 packages

Name	Type
@workflow/world-vercel	Patch
@workflow/cli	Patch
@workflow/core	Patch
@workflow/web	Patch
workflow	Patch
@workflow/world-testing	Patch
@workflow/builders	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/nuxt	Patch

Not sure what this means? Click here to learn what changesets are.

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

github-actions · 2026-09-30T01:17:11Z

🧪 E2E Test Results

✅ All tests passed

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

'hookGetConflictWithPriorStepWorkflow' - hook.getConflict() does not block step execution (nextjs-webpack · local-dev / local / node / stable)
addTenWorkflow via pages router (nextjs-webpack · local-dev / local / node / canary)
promiseAllWorkflow via pages router (nextjs-webpack · local-dev / local / node / canary)
sleepingWorkflow via pages router (nextjs-webpack · local-dev / local / node / canary)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

run-pickup-stall · runs app-generated source against a registered step (tanstack-start) · at 01:21:45Z · abandoned wrun_01M3QYE26RN12XY2ZYVBVEXTJZ
cold-start-warmup · suite warmup (tanstack-start) · at 01:21:49Z · abandoned wrun_01M3QYE27DCC8JASG17N4ZT2D9
run-pickup-stall · hookCleanupTestWorkflow - hook token reuse after workflow completion (nextjs-webpack) · at 01:29:18Z · abandoned wrun_01M3QYVVXWW20GZ5FKTX2N3VEB
run-pickup-stall · hookGetConflictWorkflow - awaiting hook.getConflict() registers hook without payload (nextjs-webpack) · at 01:29:23Z · abandoned wrun_01M3QYW187WKRQ4F0KHB18YT2Z
run-pickup-stall · 'hookGetConflictWithPriorStepWorkflow' - hook.getConflict() does not block step execution (nextjs-webpack) · at 01:29:24Z · abandoned wrun_01M3QYW2AQ51NRWQXWFJ98DVBP

E2E Test Summary

Summary

	Passed	Skipped	Total
✅ ▲ Vercel Production	3904	875	4779
✅ 💻 Local Development	4406	550	4956
✅ 📦 Local Production	4406	550	4956
✅ 🐘 Local Postgres	4406	550	4956
✅ 🪟 Windows	342	12	354
✅ 🌐 Cross-language Conformance	68	84	152
✅ dynamic-runs	0	0	0
✅ vercel-http-transport	879	183	1062
✅ vercel-multi-region	27	0	27
✅ vercel-ws-transport	595	113	708
Total	19033	2917	21950

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	142	35
✅ astro-quickjs	142	35
✅ example-node	142	35
✅ example-quickjs	142	35
✅ express-node	142	35
✅ express-quickjs	142	35
✅ fastify-node	142	35
✅ fastify-quickjs	142	35
✅ hono-node	142	35
✅ hono-quickjs	142	35
✅ nest-node	142	35
✅ nest-quickjs	142	35
✅ nextjs-turbopack-node	169	8
✅ nextjs-turbopack-quickjs	169	8
✅ nextjs-webpack-node	169	8
✅ nextjs-webpack-quickjs	169	8
✅ nitro-node	142	35
✅ nitro-quickjs	142	35
✅ nuxt-node	142	35
✅ nuxt-quickjs	142	35
✅ python-node	66	111
✅ sveltekit-node	161	16
✅ sveltekit-quickjs	161	16
✅ tanstack-start-node	142	35
✅ tanstack-start-quickjs	142	35
✅ vite-node	142	35
✅ vite-quickjs	142	35

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	148	29
✅ astro-stable-quickjs	148	29
✅ express-stable-node	148	29
✅ express-stable-quickjs	148	29
✅ fastify-stable-node	148	29
✅ fastify-stable-quickjs	148	29
✅ hono-stable-node	148	29
✅ hono-stable-quickjs	148	29
✅ nest-stable-node	148	29
✅ nest-stable-quickjs	148	29
✅ nextjs-turbopack-canary-node	176	1
✅ nextjs-turbopack-canary-quickjs	176	1
✅ nextjs-turbopack-stable-node	176	1
✅ nextjs-turbopack-stable-quickjs	176	1
✅ nextjs-webpack-canary-node	176	1
✅ nextjs-webpack-canary-quickjs	176	1
✅ nextjs-webpack-stable-node	176	1
✅ nextjs-webpack-stable-quickjs	176	1
✅ nitro-stable-node	148	29
✅ nitro-stable-quickjs	148	29
✅ nuxt-stable-node	148	29
✅ nuxt-stable-quickjs	148	29
✅ sveltekit-stable-node	167	10
✅ sveltekit-stable-quickjs	167	10
✅ tanstack-start-node	148	29
✅ tanstack-start-quickjs	148	29
✅ vite-stable-node	148	29
✅ vite-stable-quickjs	148	29

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	171	0	6
✅ nextjs-turbopack-quickjs	171	0	6

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	68	0	84

✅ dynamic-runs

App	Passed	Failed	Skipped
✅ astro-vercel	0	0	0
✅ example-vercel	0	0	0
✅ express-vercel	0	0	0
✅ fastify-vercel	0	0	0
✅ hono-vercel	0	0	0
✅ nest-vercel	0	0	0
✅ nextjs-turbopack-vercel	0	0	0
✅ nextjs-webpack-vercel	0	0	0
✅ nitro-vercel	0	0	0
✅ nuxt-vercel	0	0	0
✅ sveltekit-vercel	0	0	0
✅ tanstack-start-vercel	0	0	0
✅ vite-vercel	0	0	0

✅ vercel-http-transport

App	Passed	Skipped
✅ example	142	35
✅ express	142	35
✅ hono	142	35
✅ nextjs-turbopack	169	8
✅ nitro	142	35
✅ vite	142	35

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	142	35
✅ express	142	35
✅ nextjs-turbopack	169	8
✅ vite	142	35

📋 View full workflow run

github-actions · 2026-09-30T01:17:13Z

📊 Workflow Benchmarks

commit 854f136 · Wed, 30 Sep 2026 01:37:10 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	467 (-27%) 💚	2435 🔴 (-2.7%)	2459 🔴 (-3.6%)	2565 🔴 (-4.7%)	30
TTFS	stream	2264 (+20%) 🔻	2403 🔴 (+21%) 🔻	2411 🔴 (+20%) 🔻	2450 🔴 (+19%) 🔻	30
TTFS	hook + stream	719 (-6.1%)	2708 🔴 (+16%) 🔻	2735 🔴 (+13%)	3207 🔴 (+15%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	522 (-2.6%)	769 (-11%)	2784 (+192%) 🔻	2796 (-7.1%)	10
Fan-out TTLS	Promise.all(100 steps)	2017 (+28%) 🔻	5390 (+65%) 🔻	6513 (+86%) 🔻	10654 (+75%) 🔻	10
STSO	1020 steps (inline)	144 (-13%)	184 (-19%) 💚	203 (-20%) 💚	290 (-22%) 💚	1019
WO	1020 steps	184401 (-19%) 💚	184401 (-19%) 💚	184401 (-19%) 💚	184401 (-19%) 💚	1
CRTT	first chunk (pooled)	61 (-18%) 💚	90 (-41%) 💚	104 (-58%) 💚	338 (+20%) 🔻	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	77.5 (-31%)	124 (-30%)	148 (-45%)	294 (-22%)	92 (-32%)	10
size sweep (100/s, 160B-12KB)	81 (-32%)	134 (-27%)	189 (-28%)	493 (+17%)	120 (-43%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	91 (-40%)	141 (-18%)	170 (-21%)	262 (-35%)	186 (-38%)	3
replay eve-gpt-5.6-sol-2000t (1x)	82.5 (-47%)	154 (-12%)	801 (+253%)	4461 (+16%)	2262 (+14%)	2
replay eve-gpt-5.6-sol-2000t (2x)	77 (-49%)	146 (-39%)	188 (-42%)	389 (-28%)	161 (-46%)	3

📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 226997ms → this run 183863ms (Δ -43134ms, -19%)

  100-150 ms  ┃                         main   0  this   6    +6
  150-200 ms  ████████░░░░░░░░░░░░░░░┃  main 301  this 877  +576
  200-250 ms  ██┃█████████████          main 592  this 112  -480
  250-300 ms  ┃██                       main  95  this  17   -78
  300-350 ms  ┃                         main  19  this   6   -13
  350-400 ms  ┃                         main   5  this   0    -5
  400-450 ms  ┃                         main   2  this   0    -2
  450-500 ms  ┃                         main   2  this   1    -1
  700-750 ms  ┃                         main   1  this   0    -1
1500-1550 ms  ┃                         main   1  this   0    -1
3650-3700 ms  ┃                         main   1  this   0    -1

📈 CRTT drill-down vs main (RTT distributions & profiles)

variant  RTT 1ms→5s+             avg         p50          p90          p99     n
control  ······▆█▁····  106.1 (-29%)  105 (-24%)   148 (-45%)   294 (-22%)  3000
sweep    ······▆█▁▁···  117.6 (-25%)  106 (-25%)   189 (-28%)   493 (+17%)  3000
gw 1x    ·····▁▅█▁····  113.9 (-21%)  109 (-20%)   170 (-21%)   262 (-35%)  5295
eve 1x   ·····▁▅█▁▁▁▁·  255.3 (+31%)  106 (-23%)  801 (+253%)  4461 (+16%)  5186
eve 2x   ·····▁▅█▁····    123 (-34%)  114 (-29%)   188 (-42%)   389 (-28%)  7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control  █▅▂▂▇▆▂▁▂▂  102–112ms
sweep    ▃█▃▂▄▄▄▄▂▁  110–132ms
gw 1x    ▂▅▁█▂▂▃▁▁▂  108–135ms
eve 1x   ▁█▄▁▁▁▁▁▁▁  107–1151ms
eve 2x   ▃▁▂▃▂▃▆█▂▁  111–157ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep  ▄█▅▅▆▃▁  115–120ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control  ▇▄▇▂█▁▄▄▄▅  29–36ms
sweep    ▆▅▅█▄▅▇▇▅▁  41–55ms
gw 1x    ▃█▂▅▃▅▂▃▁▄  30–38ms
eve 1x   ▂█▁▁▁▂▂▂▃▃  19–50ms
eve 2x   ▅▄▃▅█▂▅▁▂█  18–24ms

ℹ️ Metric definitions & methodology

_{Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.}

_{The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.}

_{The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.}

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles}

_{Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600}

_{All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).}

_{Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.}

github-actions · 2026-09-30T01:20:46Z

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 42 total

fence=per-spec

scenario	outcome	events	virt	replay
✅ `smoke-no-steps`	completed	3	0ms	ok
✅ `smoke-one-step`	completed	6	0ms	ok
✅ `hook-at-step-started`	completed	12	0ms	ok
✅ `hook-at-step-completed`	completed	12	0ms	ok
✅ `hook-at-hook-created`	completed	12	0ms	ok
✅ `deadline-hook-wins`	completed	7	1.0h	ok
✅ `deadline-expires`	completed	7	1.0h	ok
✅ `step-vs-timer-early-settlement`	completed	8	1.0h	ok
✅ `long-sleep`	completed	11	30.0d	ok
✅ `hook-never-arrives`	stalled	3	0ms	skipped
✅ `step-retries-twice`	completed	10	2.0s	ok
✅ `parallel-steps`	completed	9	0ms	ok
✅ `hook-on-execution-state`	completed	12	0ms	ok
✅ `peek-hook-before-branch`	completed	12	0ms	ok
✅ `peek-hook-after-branch`	completed	12	0ms	ok
✅ `peek-hook-at-registration`	completed	12	0ms	ok
✅ `race-hook-before-probe`	completed	12	0ms	ok
✅ `race-hook-after-probe`	completed	12	0ms	ok
✅ `race-duplicate-delivery`	completed	13	0ms	ok
✅ `attr-hook-before-step`	completed	11	0ms	ok
✅ `attr-hook-after-step`	completed	11	0ms	ok
✅ `attr-from-step-body`	completed	13	0ms	ok
✅ `fork-hook-after-timeout`	completed	14	1.0m	ok
✅ `fork-hook-before-timeout`	completed	14	1.0m	ok
✅ `count-hook-after-timeout`	completed	17	1.0m	ok
✅ `count-hook-before-timeout`	completed	20	1.0m	ok
✅ `stale-read-step-count-fork`	completed	20	1.0m	ok
✅ `stale-read-equal-step-counts`	completed	14	1.0m	ok
✅ `step-vs-step-fork`	completed	12	0ms	ok
✅ `step-vs-step-fork-fenced`	completed	12	0ms	ok
✅ `fence-catches-benign-direction`	completed	12	5ms	ok
✅ `in-flight-before-decision`	completed	17	1.0m	ok
❌ `in-flight-before-decision-counted`	completed	17	1.0m	ok
✅ `in-flight-after-decision`	completed	19	2.0m	ok
✅ `stale-read-step-count-fork-fenced`	completed	20	1.0m	ok
✅ `fork-hook-wins`	completed	13	1.0m	ok
✅ `fork-timeout-wins`	completed	13	1.0m	ok
✅ `unclaimed-payload-under-fork`	completed	17	1.0m	ok
✅ `claimed-payload-under-fork`	completed	17	1.0m	ok
✅ `writers-independent-step-bodies`	completed	12	0ms	ok
✅ `writers-scripted-tempo`	completed	12	0ms	ok
✅ `cancel-mid-step`	cancelled	7	0ms	skipped

Full trace: world-sim.txt

github-actions · 2026-09-30T01:22:19Z

Framework	Flow route	Step reg.	Framework output
hono	265.9 KiB (±0)	97.2 KiB (±0)	1.98 MiB (+1.6 KiB)
nextjs-turbopack	273.3 KiB (±0)	426 B (±0)	979.8 KiB (+739 B)

About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

854f136 · run

shalabhc · 2026-09-30T03:28:48Z

Closing in favour of #4504, which splits large frames so the transport works where a single WebSocket message is size-limited.

fix(world-vercel): resume an in-flight step_started after a lost WebS…

854f136

…ocket connection Co-Authored-By: Shalabh Chaturvedi <7066873+shalabhc@users.noreply.github.com>

shalabhc requested a review from a team as a code owner September 30, 2026 01:16

vercel Bot deployed to Preview – workflow-docs September 30, 2026 01:19 View deployment

shalabhc closed this Sep 30, 2026

Navigation Menu

Repository navigation

fix(world-vercel): resume an in-flight step_started after a lost WebSocket connection - #4502

fix(world-vercel): resume an in-flight step_started after a lost WebSocket connection#4502
shalabhc wants to merge 1 commit into
mainfrom
switch-ai-gateway-transport-from-http-to-websock-resumable-ws

shalabhc commented Sep 30, 2026

Uh oh!

vercel Bot commented Sep 30, 2026 •

edited

Loading

Uh oh!

changeset-bot Bot commented Sep 30, 2026

Uh oh!

github-actions Bot commented Sep 30, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 30, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 30, 2026

Uh oh!

github-actions Bot commented Sep 30, 2026

Uh oh!

shalabhc commented Sep 30, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

shalabhc commented Sep 30, 2026

Problem

Change

Tests

Uh oh!

vercel Bot commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

changeset-bot Bot commented Sep 30, 2026

🦋 Changeset detected

Uh oh!

github-actions Bot commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 E2E Test Results

⚠️ Flaky E2E Tests (passed on retry)

🛠 Infra Events (absorbed by the harness)

E2E Test Summary

Uh oh!

github-actions Bot commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Workflow Benchmarks

Uh oh!

github-actions Bot commented Sep 30, 2026

Sim World

Uh oh!

github-actions Bot commented Sep 30, 2026

Uh oh!

shalabhc commented Sep 30, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

vercel Bot commented Sep 30, 2026 •

edited

Loading

github-actions Bot commented Sep 30, 2026 •

edited

Loading

github-actions Bot commented Sep 30, 2026 •

edited

Loading