[core] Fail dev HMR cleanup on a stranded step registration by VaguelySerious · Pull Request #3682 · vercel/workflow

VaguelySerious · 2026-08-19T22:49:18Z

Problem

Three of the last 120 Tests runs had E2E Windows Tests (node) burn its full ~30-minute
window and get cancelled with every e2e test failing on
[world-local] Queue message failed (HTTP 500), where the handlerError is a Next.js
_error page rather than anything workflow-shaped:

job	flow-route 500s	stranded-import errors
96228253373	10,135	20,346
96214515530	10,218	10,886
96202855009	10,280	20,557

The flow route never answered a single request successfully in any of them. The dev server
log says why:

⨯ app/.well-known/workflow/v1/flow/__step_registrations.js:33:1
Module not found: Can't resolve '../../../../../workflows/source-map-warning-fixture.ts'

dev.test.ts > "should not log source map warnings for workflow node_modules imports"
writes workflows/source-map-warning-fixture.ts, which declares a 'use step' function,
and its afterEach deletes it. The generated __step_registrations.js imports every
discovered step file by path, so that deletion only stops breaking the flow route once a
rediscovery regenerates the file. When the watcher drops the unlink — which is what happens
on Windows — the generated file keeps importing a path that no longer exists, the flow route
stops compiling, and every workflow dispatch for the rest of the job gets a 500 pointing at
a fixture from a test that already passed.

The HMR log confirms nothing recovers it: 164 → 165 → 166 → 165 → 165 workflows, then
three skips and no further rediscovery. afterEach's prewarm() only waits for
workflow dev hmr: ready, printed once at startup, so nothing ever waited for the
post-deletion rediscovery in the first place.

The generated workflow bundle inlines workflow sources instead of importing them, so only
step-declaring fixtures can strand it. That is why new-workflow.ts leaks harmlessly in
the same runs while the source-map fixture is fatal.

The existing fail-fast guard cannot see this

The Windows job already probes the dev server before the long e2e run, precisely to avoid
burning the job window on a wedged server. It probes GET /api/chat, which compiles
independently of the flow route, so it reported -> 405 and let the suite run in all three
jobs.

Changes

packages/core/e2e/dev.test.ts — after deleting fixtures, cleanup waits for the
generated step registrations to stop importing them. If they still do when the budget
runs out, the fixture contents are written back so the shared dev server keeps serving
the rest of the suite, and the hook fails naming the stranded file. CI already skips the
e2e suite when dev.test.ts fails, so this turns a 30-minute burn with ~10k misleading
500s into an immediate, accurate failure. The convergence wait runs before the
node_modules fixture-package removal so a restored fixture still resolves its import.
.github/workflows/tests.yml — the pre-e2e probe now POSTs
/.well-known/workflow/v1/flow?__health, the SDK's own health endpoint on the route
that actually breaks. It returns 200 on a healthy dev server and would have returned 500
in all three jobs above.

Validation

Run locally against workbench/nextjs-turbopack on macOS (all 9 dev tests, so including
the flow-route HMR fuzz cases that also delete step-declaring files):

Happy path: the convergence wait never trips on any of the tests that delete fixtures. A
deletion converges in ~2s, so the watcher path itself is sound and the Windows miss is the
discriminator.
should follow Next flow-route HMR rebuild rules for body-only changes fails on macOS
(expected 2 to be 1 on an exact HMR log count). It fails identically with unmodified
origin/main's dev.test.ts against the same dev server, so it is pre-existing and
unrelated. That case is skipped on Windows.
Forced-failure path (convergence budget shortened so it always expires): the hook fails
with the stranded path named, the fixture is restored, and
POST /.well-known/workflow/v1/flow?__health still answers 200.
POST /.well-known/workflow/v1/flow?__health returns 200 on a healthy dev server and 500
when a path reachable from __step_registrations.js does not resolve, while
GET /api/chat keeps answering 405 — the asymmetry the second change fixes.

The underlying Windows watcher miss is worth chasing separately; this PR stops it from
costing a whole job and makes it name itself.

Note on a related hole, not changed here

The Linux e2e-local-dev lane runs pnpm vitest run packages/core/e2e/dev.test.ts; sleep 10
and then continues into the full e2e suite, so a dev.test.ts failure there is discarded.
That lane would swallow the new hook failure too. Tightening it would newly red the lane on
pre-existing dev.test.ts flakes (the flow-route HMR fuzz case already fails on macOS
against unmodified main, see below), so it seemed worth raising separately rather than
bundling in.

`dev.test.ts` fixtures that declare a `'use step'` function are imported by path from the generated `__step_registrations.js`, so deleting one only stops breaking the flow route once a rediscovery regenerates that file. When the dev server's watcher drops the unlink, the generated file keeps importing a path that no longer exists: the flow route stops compiling and every later workflow dispatch in the job gets a 500 that names a fixture from a test that already passed. Three of the last 120 `Tests` runs lost the whole ~30-minute Windows e2e window this way, each with ~10k flow-route 500s and no successful dispatch. Cleanup now waits for the generated step registrations to drop every file it deleted. If they still reference one when the budget expires, the fixture is written back so the shared dev server keeps serving the rest of the suite, and the hook fails naming the stranded path. The wait runs before the node_modules fixture-package removal so a restored fixture still resolves its import. The pre-e2e probe moves from `GET /api/chat` to `POST /.well-known/workflow/v1/flow?__health`. /api/chat compiles independently of the flow route, so it answered 405 in all three jobs while every dispatch was getting a 500. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

changeset-bot · 2026-08-19T22:49:23Z

🦋 Changeset detected

Latest commit: 62fcd0f

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

This PR includes changesets to release 16 packages

Name	Type
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/vitest	Patch
@workflow/web-shared	Patch
@workflow/web	Patch
workflow	Patch
@workflow/world-testing	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

vercel · 2026-08-19T22:49:35Z

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview	Aug 19, 2026 10:52pm
example-nextjs-workflow-webpack	Ready	Preview	Aug 19, 2026 10:52pm
example-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-astro-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-express-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-fastify-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-hono-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-nestjs-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-nitro-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-nuxt-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-python-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-sveltekit-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-tanstack-start-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workbench-vite-workflow	Ready	Preview	Aug 19, 2026 10:52pm
workflow-docs	Ready	Preview, v0	Aug 19, 2026 10:52pm
workflow-swc-playground	Ready	Preview	Aug 19, 2026 10:52pm
workflow-tarballs	Ready	Preview	Aug 19, 2026 10:52pm
workflow-web	Ready	Preview	Aug 19, 2026 10:52pm

github-actions · 2026-08-19T22:49:37Z

🧪 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.

abortVoidSleepTimeoutWorkflow: documented void sleep().then(abort) pattern works (nest)

E2E Test Summary

Summary

	Passed	Skipped	Total
✅ ▲ Vercel Production	3474	738	4212
✅ 💻 Local Development	3810	558	4368
✅ 📦 Local Production	3810	558	4368
✅ 🐘 Local Postgres	3810	558	4368
✅ 🪟 Windows	312	0	312
✅ 🌐 Cross-language Conformance	9	128	137
✅ vercel-multi-region	27	0	27
Total	15252	2540	17792

Details by Category

✅ ▲ Vercel Production

App	Passed	Skipped
✅ astro-node	128	28
✅ astro-quickjs	128	28
✅ example-node	128	28
✅ example-quickjs	128	28
✅ express-node	128	28
✅ express-quickjs	128	28
✅ fastify-node	128	28
✅ fastify-quickjs	128	28
✅ hono-node	128	28
✅ hono-quickjs	128	28
✅ nest-node	128	28
✅ nest-quickjs	128	28
✅ nextjs-turbopack-node	153	3
✅ nextjs-turbopack-quickjs	153	3
✅ nextjs-webpack-node	153	3
✅ nextjs-webpack-quickjs	153	3
✅ nitro-node	128	28
✅ nitro-quickjs	128	28
✅ nuxt-node	128	28
✅ nuxt-quickjs	128	28
✅ python-node	8	148
✅ sveltekit-node	147	9
✅ sveltekit-quickjs	147	9
✅ tanstack-start-node	128	28
✅ tanstack-start-quickjs	128	28
✅ vite-node	128	28
✅ vite-quickjs	128	28

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	130	26
✅ astro-stable-quickjs	130	26
✅ express-stable-node	130	26
✅ express-stable-quickjs	130	26
✅ fastify-stable-node	130	26
✅ fastify-stable-quickjs	130	26
✅ hono-stable-node	130	26
✅ hono-stable-quickjs	130	26
✅ nest-stable-node	130	26
✅ nest-stable-quickjs	130	26
✅ nextjs-turbopack-canary-node	137	19
✅ nextjs-turbopack-canary-quickjs	137	19
✅ nextjs-turbopack-stable-node	156	0
✅ nextjs-turbopack-stable-quickjs	156	0
✅ nextjs-webpack-canary-node	137	19
✅ nextjs-webpack-canary-quickjs	137	19
✅ nextjs-webpack-stable-node	156	0
✅ nextjs-webpack-stable-quickjs	156	0
✅ nitro-stable-node	130	26
✅ nitro-stable-quickjs	130	26
✅ nuxt-stable-node	130	26
✅ nuxt-stable-quickjs	130	26
✅ sveltekit-stable-node	149	7
✅ sveltekit-stable-quickjs	149	7
✅ tanstack-start-node	130	26
✅ tanstack-start-quickjs	130	26
✅ vite-stable-node	130	26
✅ vite-stable-quickjs	130	26

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	130	26
✅ astro-stable-quickjs	130	26
✅ express-stable-node	130	26
✅ express-stable-quickjs	130	26
✅ fastify-stable-node	130	26
✅ fastify-stable-quickjs	130	26
✅ hono-stable-node	130	26
✅ hono-stable-quickjs	130	26
✅ nest-stable-node	130	26
✅ nest-stable-quickjs	130	26
✅ nextjs-turbopack-canary-node	137	19
✅ nextjs-turbopack-canary-quickjs	137	19
✅ nextjs-turbopack-stable-node	156	0
✅ nextjs-turbopack-stable-quickjs	156	0
✅ nextjs-webpack-canary-node	137	19
✅ nextjs-webpack-canary-quickjs	137	19
✅ nextjs-webpack-stable-node	156	0
✅ nextjs-webpack-stable-quickjs	156	0
✅ nitro-stable-node	130	26
✅ nitro-stable-quickjs	130	26
✅ nuxt-stable-node	130	26
✅ nuxt-stable-quickjs	130	26
✅ sveltekit-stable-node	149	7
✅ sveltekit-stable-quickjs	149	7
✅ tanstack-start-node	130	26
✅ tanstack-start-quickjs	130	26
✅ vite-stable-node	130	26
✅ vite-stable-quickjs	130	26

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	130	26
✅ astro-stable-quickjs	130	26
✅ express-stable-node	130	26
✅ express-stable-quickjs	130	26
✅ fastify-stable-node	130	26
✅ fastify-stable-quickjs	130	26
✅ hono-stable-node	130	26
✅ hono-stable-quickjs	130	26
✅ nest-stable-node	130	26
✅ nest-stable-quickjs	130	26
✅ nextjs-turbopack-canary-node	137	19
✅ nextjs-turbopack-canary-quickjs	137	19
✅ nextjs-turbopack-stable-node	156	0
✅ nextjs-turbopack-stable-quickjs	156	0
✅ nextjs-webpack-canary-node	137	19
✅ nextjs-webpack-canary-quickjs	137	19
✅ nextjs-webpack-stable-node	156	0
✅ nextjs-webpack-stable-quickjs	156	0
✅ nitro-stable-node	130	26
✅ nitro-stable-quickjs	130	26
✅ nuxt-stable-node	130	26
✅ nuxt-stable-quickjs	130	26
✅ sveltekit-stable-node	149	7
✅ sveltekit-stable-quickjs	149	7
✅ tanstack-start-node	130	26
✅ tanstack-start-quickjs	130	26
✅ vite-stable-node	130	26
✅ vite-stable-quickjs	130	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	156	0	0
✅ nextjs-turbopack-quickjs	156	0	0

✅ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
✅ python	9	0	128

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

📋 View full workflow run

github-actions · 2026-08-19T22:49:37Z

📊 Workflow Benchmarks

commit 62fcd0f · Wed, 19 Aug 2026 23:10:40 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	1287 (+24%) 🔻	1401 🔴 (+19%) 🔻	1442 🔴 (+17%) 🔻	1732 🔴 (+4.1%)	30
TTFS	stream	1260 (+25%) 🔻	1388 🔴 (+25%) 🔻	1428 🔴 (+25%) 🔻	1742 🔴 (+49%) 🔻	30
TTFS	hook + stream	538 (-58%) 💚	1644 🔴 (+15%)	1690 🔴 (+15%)	1986 🔴 (+26%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	527 (-7.9%)	829 (-16%) 💚	986 (-45%) 💚	2498 (+38%) 🔻	10
Fan-out TTLS	Promise.all(100 steps)	4804 (+1.2%)	8742 (+6.0%)	9471 (-13%)	10733 (-19%) 💚	10
STSO	1020 steps (inline)	117 (-5.6%)	159 (-35%) 💚	185 (-37%) 💚	303 (-40%) 💚	1019
WO	1020 steps	158021 (-33%) 💚	158021 (-33%) 💚	158021 (-33%) 💚	158021 (-33%) 💚	1
CRTT	first chunk (pooled)	101 (-4.7%)	175 (+3.6%)	372 (+84%) 🔻	3550 (+770%) 🔻	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	115 (-20%)	131 (-27%)	168 (-42%)	335 (-36%)	96.5 (-32%)	10
size sweep (100/s, 160B-12KB)	127 (-9%)	135 (-26%)	172 (-32%)	310 (-31%)	134 (-14%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	204 (+37%)	139 (-4%)	230 (+8%)	675 (-3%)	293 (+18%)	3
replay eve-gpt-5.6-sol-2000t (1x)	1837 (+1128%)	140 (-5%)	193 (±0%)	3960 (+1082%)	2212 (+683%)	2
replay eve-gpt-5.6-sol-2000t (2x)	372 (+120%)	242 (+12%)	468 (+23%)	1195 (±0%)	226 (-43%)	3

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

1020 steps (inline)

Cumulative STSO time: main 236286ms → this run 157785ms (Δ -78501ms, -33%)

 100-150 ms  █░░░░░░░░░░░░░░░░░░░░░░┃  main  16  this 623  +607
 150-200 ms  ██████████░░┃             main 251  this 326   +75
 200-250 ms  ┃███████████████████      main 513  this  38  -475
 250-300 ms  ┃█████                    main 153  this  20  -133
 300-350 ms  ┃█                        main  42  this   8   -34
 350-400 ms  ┃                         main  21  this   3   -18
 400-450 ms  ┃                         main  10  this   0   -10
 450-500 ms  ┃                         main   2  this   0    -2
 500-550 ms  ┃                         main   6  this   0    -6
 550-600 ms  ┃                         main   0  this   1    +1
 600-650 ms  ┃                         main   2  this   0    -2
 650-700 ms  ┃                         main   2  this   0    -2
950-1000 ms  ┃                         main   1  this   0    -1

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

variant  RTT 1ms→5s+             avg         p50         p90            p99     n
control  ······▆█▁····  110.9 (-24%)  105 (-21%)  168 (-42%)     335 (-36%)  3000
sweep    ······▅█▁····  114.9 (-21%)  107 (-20%)  172 (-32%)     310 (-31%)  3000
gw 1x    ·····▁▆█▁▁···   119.7 (-9%)  105 (-11%)   230 (+8%)      675 (-3%)  5295
eve 1x   ·····▁▆█▁▁·▁·  186.6 (+44%)  104 (-11%)   193 (±0%)  3960 (+1082%)  5186
eve 2x   ·····▁▃█▃▁▁··   175.5 (-9%)  132 (-14%)  468 (+23%)     1195 (±0%)  7779

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

control  █▃▃▅▂▁▂▂▂▃  103–130ms
sweep    █▆▃▄▄▂▁▂▅▂  104–132ms
gw 1x    █▄▂▂▁▁▁▁▂▁  101–197ms
eve 1x   ▁▁▁▁▁▁▁▁▁█  101–801ms
eve 2x   █▁▂▁▁▁▂▅▂▁  123–364ms

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

sweep  ▂▃▇█▅▂▁  113–117ms

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

control  ▁▆▄█▁▃▆▄▅▄  28–37ms
sweep    ▃▆▃█▂▇▄▃▁▂  41–51ms
gw 1x    █▃▄▂▄▃▄▄▄▁  26–42ms
eve 1x   ▂▁▁▂▁▁▂▁▁█  22–53ms
eve 2x   █▂▁▁▂▁▂▂▂▃  20–43ms

ℹ️ 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-08-19T22:52:51Z

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 41 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
✅ `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

vercel Bot deployed to Preview – workbench-python-workflow August 19, 2026 22:49 View deployment

vercel Bot deployed to Preview – workflow-web August 19, 2026 22:50 View deployment

vercel Bot deployed to Preview – workbench-hono-workflow August 19, 2026 22:50 View deployment

vercel Bot deployed to Preview – workbench-express-workflow August 19, 2026 22:50 View deployment

vercel Bot deployed to Preview – workbench-nestjs-workflow August 19, 2026 22:50 View deployment

vercel Bot deployed to Preview – workflow-tarballs August 19, 2026 22:50 View deployment

vercel Bot deployed to Preview – example-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workbench-nitro-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workbench-astro-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – example-nextjs-workflow-webpack August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workbench-fastify-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workbench-vite-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workbench-tanstack-start-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workbench-sveltekit-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workbench-nuxt-workflow August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – example-nextjs-workflow-turbopack August 19, 2026 22:51 View deployment

vercel Bot deployed to Preview – workflow-docs August 19, 2026 22:52 View deployment

vercel Bot deployed to Preview – workflow-swc-playground August 19, 2026 22:52 View deployment

Navigation Menu

Uh oh!

[core] Fail dev HMR cleanup on a stranded step registration - #3682

[core] Fail dev HMR cleanup on a stranded step registration#3682
VaguelySerious wants to merge 1 commit into
mainfrom
peter/windows-step-registration-cleanup

VaguelySerious commented Aug 19, 2026

Uh oh!

changeset-bot Bot commented Aug 19, 2026

Uh oh!

vercel Bot commented Aug 19, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 19, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 19, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

VaguelySerious commented Aug 19, 2026

Problem

The existing fail-fast guard cannot see this

Changes

Validation

Note on a related hole, not changed here

Uh oh!

changeset-bot Bot commented Aug 19, 2026

🦋 Changeset detected

Uh oh!

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

Uh oh!

Uh oh!

github-actions Bot commented Aug 19, 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)

E2E Test Summary

Uh oh!

github-actions Bot commented Aug 19, 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 Aug 19, 2026

Sim World

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

vercel Bot commented Aug 19, 2026 •

edited

Loading

github-actions Bot commented Aug 19, 2026 •

edited

Loading

github-actions Bot commented Aug 19, 2026 •

edited

Loading