[vercel-gh-bot-2]

This PR was automatically created to test a workflow-server preview deployment.

---

This PR will be automatically closed after 24 hours.

[vercel]

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

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

[github-actions]

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

▲ Vercel Production (31 failed)

nuxt-node (31 failed):

• error handling error propagation workflow errors nested function calls preserve message and stack trace
• error handling error propagation workflow errors cross-file imports preserve message and stack trace
• error handling error propagation step errors basic step error preserves message and stack trace
• error handling error propagation step errors cross-file step error preserves message and function names in stack
• error handling catchability FatalError can be caught and detected with FatalError.is()
• error handling catchability step throw round-trips FatalError with cause chain to workflow catch
• error handling catchability workflow throw round-trips FatalError + cause through run_failed event
• error handling catchability workflow throw of a non-Error value round-trips verbatim as cause
• error handling catchability step throw of a non-Error value preserves it as cause on the wrapping FatalError
• error handling serialization failures step-argument serialization failure is catchable in workflow code
• error handling serialization failures uncaught step-argument serialization failure fails the run as USER_ERROR without redelivery retries
• error handling serialization failures step-return-value serialization failure is catchable in workflow code
• error handling serialization failures uncaught step-return-value serialization failure fails the run as USER_ERROR
• error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
• error handling not registered StepNotRegisteredError fails the step but workflow can catch it
• concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_41M5JR1T750GVNJZ0T0KM4G7AS | 🔍 observability
• hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_41M5JR3GDM0GKC2TVJZ4QJF73G | 🔍 observability
• hookTokenReuseLoopWorkflow - same run recreates a hook with the same token after dispose() | wrun_41M5JR3DWE0GH4YYVEZB77P27D | 🔍 observability
• stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_41M5JR3MPA0GWN3WV73CVR8Q64 | 🔍 observability
• stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_41M5JR3V8Z0GJ804PFTSH7AK1C | 🔍 observability
• spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_41M5JR424J0GPK6CXFDA704KV8 | 🔍 observability
• runClassSerializationWorkflow - Run instances serialize across workflow/step boundaries | wrun_41M5JR427K0GYX4V188RFHW4E2 | 🔍 observability
• pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_41M5JR49SV0GSF03FDBPRPM1WA | 🔍 observability
• Calculator.calculate - static workflow method using static step methods from another class | wrun_41M5JR4CWN0GRE7GV2CNPC1DZT | 🔍 observability
• AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_41M5JR4DNW0GJ42NYXA2FG0YGB | 🔍 observability
• ChainableService.processWithThis - static step methods using this to reference the class | wrun_41M5JR4GWQ0GYYKGA0328AJRZ9 | 🔍 observability
• thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_41M5JR4JXE0GX1FCKRDYXCTV73 | 🔍 observability
• customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_41M5JR4KQH0GPX1J8678D24QTD | 🔍 observability
• instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_41M5JR4RKJ0GY0K0E6SBMN6Z10 | 🔍 observability
• crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_41M5JR4S8B0GWDFXWW6MFMKVW0 | 🔍 observability
• stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_41M5JR4W0B0GHVJZQPS6VG3RE9 | 🔍 observability

⚠️ 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.

• cancelRun - cancelling a running workflow (nuxt · vercel-prod / vercel / node / production)
• hookCleanupTestWorkflow - hook token reuse after workflow completion (nuxt · vercel-prod / vercel / node / production)
• hookGetConflictWorkflow - hook.getConflict() resolves with the conflicting run when token is already registered (nuxt · vercel-prod / vercel / node / production)
• hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep (nuxt · vercel-prod / vercel / node / production)
• sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) (nuxt · vercel-prod / vercel / node / production)

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
❌ ▲ Vercel Production	3951	31	878	4860
✅ dynamic-runs	0	0	0	0
✅ vercel-http-transport	897	0	183	1080
✅ vercel-multi-region	27	0	0	27
✅ vercel-ws-transport	607	0	113	720
Total	5482	31	1174	6687

Details by Category

❌ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro-node	145	0	35
✅ astro-quickjs	145	0	35
✅ example-node	145	0	35
✅ example-quickjs	145	0	35
✅ express-node	145	0	35
✅ express-quickjs	145	0	35
✅ fastify-node	145	0	35
✅ fastify-quickjs	145	0	35
✅ hono-node	145	0	35
✅ hono-quickjs	145	0	35
✅ nest-node	145	0	35
✅ nest-quickjs	145	0	35
✅ nextjs-turbopack-node	172	0	8
✅ nextjs-turbopack-quickjs	172	0	8
✅ nextjs-webpack-node	172	0	8
✅ nextjs-webpack-quickjs	172	0	8
✅ nitro-node	145	0	35
✅ nitro-quickjs	145	0	35
❌ nuxt-node	114	31	35
✅ nuxt-quickjs	145	0	35
✅ python-node	66	0	114
✅ sveltekit-node	164	0	16
✅ sveltekit-quickjs	164	0	16
✅ tanstack-start-node	145	0	35
✅ tanstack-start-quickjs	145	0	35
✅ vite-node	145	0	35
✅ vite-quickjs	145	0	35

✅ 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	Failed	Skipped
✅ example	145	0	35
✅ express	145	0	35
✅ hono	145	0	35
✅ nextjs-turbopack	172	0	8
✅ nitro	145	0	35
✅ vite	145	0	35

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Failed	Skipped
✅ example	145	0	35
✅ express	145	0	35
✅ nextjs-turbopack	172	0	8
✅ vite	145	0	35

---

📋 View full workflow run

[github-actions]

Sim World

Simulated world deterministic testing for races. Traces

🟢 world-sim scenario book — 0 fail of 42 total

fence=per-spec

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

Full trace: world-sim.txt

[github-actions]

Framework	Flow route	Step reg.	Framework output
hono	267.6 KiB (±0)	95.6 KiB (±0)	2.00 MiB (+9 B)
nextjs-turbopack	275.0 KiB (±0)	426 B (±0)	974.6 KiB (-17 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.

adda0bd · run

[changeset-bot]

⚠️ No Changeset found

Latest commit: adda0bd

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