Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Add x-workflow-run-id header to queue messages by pranaygp · Pull Request #922 · vercel/workflow · GitHub
Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add x-workflow-run-id header to queue messages by pranaygp · Pull Request #922 · vercel/workflow · GitHub
Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add x-workflow-run-id header to queue messages by pranaygp · Pull Request #922 · vercel/workflow · GitHub
Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Add x-workflow-run-id header to queue messages by pranaygp · Pull Request #922 · vercel/workflow · GitHub
Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add x-workflow-run-id header to queue messages by pranaygp · Pull Request #922 · vercel/workflow · GitHub
Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Add x-workflow-run-id header to queue messages by pranaygp · Pull Request #922 · vercel/workflow · GitHub
Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Add x-workflow-run-id header to queue messages by pranaygp · Pull Request #922 · vercel/workflow · GitHub
Skip to content

Add x-workflow-run-id header to queue messages - #922

Merged
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers
Feb 5, 2026
Merged

Add x-workflow-run-id header to queue messages#922
pranaygp merged 3 commits into
mainfrom
pranaygp/queue-headers

Conversation

@pranaygp

Copy link
Copy Markdown
Contributor

Summary

  • Add headers field to QueueOptions interface in @workflow/world
  • Pass headers through to VQS client in @workflow/world-vercel
  • Include x-workflow-run-id header in all queueMessage() calls from step-handler and suspension-handler

This enables correlation of queue messages with workflow runs for better observability.

Dependencies

Test plan

  • @workflow/core tests pass
  • @workflow/world-vercel builds successfully
  • E2E testing after VQS dependencies are merged

🤖 Generated with Claude Code

@vercel

vercelBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Feb 3, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1f4bfa8

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

This PR includes changesets to release 19 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/web-sharedPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/docs-typecheckPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

Some tests failed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production479038517
✅ 💻 Local Development438032470
✅ 📦 Local Production438032470
✅ 🐘 Local Postgres438032470
✅ 🪟 Windows470047
❌ 🌍 Community Worlds311690200
✅ 📋 Other129012141
Total20001691462315

❌ Failed Tests

🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • 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 retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro4304
✅ example4304
✅ express4304
✅ fastify4304
✅ hono4304
✅ nextjs-turbopack4601
✅ nextjs-webpack4601
✅ nitro4304
✅ nuxt4304
✅ sveltekit4304
✅ vite4304
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable4304
✅ express-stable4304
✅ fastify-stable4304
✅ hono-stable4304
✅ nextjs-turbopack-stable4700
✅ nextjs-webpack-stable4700
✅ nitro-stable4304
✅ nuxt-stable4304
✅ sveltekit-stable4304
✅ vite-stable4304
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack4700
❌ 🌍 Community Worlds
AppPassedFailedSkipped
✅ mongodb-dev300
❌ mongodb5420
✅ redis-dev300
❌ redis5420
✅ starter-dev300
❌ starter4430
✅ turso-dev300
❌ turso5420
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable4304
✅ e2e-local-postgres-nest-stable4304
✅ e2e-local-prod-nest-stable4304

📋 View full workflow run

@github-actions

github-actionsBot commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Nitro0.042s (-3.7%)1.007s (~)0.965s101.00x
💻 LocalNext.js (Turbopack)0.043s (+7.8% 🔺)1.020s (~)0.977s101.03x
💻 LocalExpress0.043s (+1.2%)1.008s (~)0.965s101.05x
🐘 PostgresNext.js (Turbopack)0.111s (-69.6% 🟢)1.022s (~)0.911s102.66x
🐘 PostgresNitro0.176s (+20.8% 🔺)1.015s (-0.8%)0.838s104.24x
🐘 PostgresExpress0.289s (+16.2% 🔺)1.013s (~)0.724s106.95x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express0.650s (-5.4% 🟢)1.660s (+5.3% 🔺)1.010s101.00x
▲ VercelNitro0.653s (-4.6%)1.606s (-7.3% 🟢)0.952s101.01x
▲ VercelNext.js (Turbopack)0.709s (+7.1% 🔺)1.668s (-16.8% 🟢)0.959s101.09x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 1 step

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.090s (~)2.013s (~)0.923s101.00x
💻 LocalNitro1.114s (~)2.007s (~)0.893s101.02x
💻 LocalExpress1.118s (~)2.009s (~)0.891s101.03x
🐘 PostgresNext.js (Turbopack)1.870s (-13.0% 🟢)2.020s (-33.1% 🟢)0.150s101.72x
🐘 PostgresExpress2.154s (+13.9% 🔺)3.013s (+49.6% 🔺)0.859s101.98x
🐘 PostgresNitro2.370s (-4.9%)3.014s (~)0.645s102.17x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.785s (-7.7% 🟢)3.741s (-1.8%)0.956s101.00x
▲ VercelNext.js (Turbopack)2.865s (-0.9%)3.699s (+1.7%)0.834s101.03x
▲ VercelNitro2.878s (+1.1%)3.665s (-5.9% 🟢)0.787s101.03x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

workflow with 10 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)10.716s (~)11.016s (~)0.299s31.00x
💻 LocalNitro10.824s (~)11.015s (~)0.191s31.01x
💻 LocalExpress10.832s (~)11.017s (~)0.185s31.01x
🐘 PostgresNext.js (Turbopack)15.202s (-25.8% 🟢)16.041s (-23.8% 🟢)0.839s21.42x
🐘 PostgresExpress20.293s (+32.7% 🔺)21.030s (+31.2% 🔺)0.737s21.89x
🐘 PostgresNitro20.423s (~)21.028s (~)0.605s21.91x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)22.872s (+1.6%)23.580s (+0.8%)0.708s21.00x
▲ VercelNitro23.319s (+3.7%)24.085s (+4.5%)0.766s21.02x
▲ VercelExpress24.172s (+4.7%)25.160s (+5.8% 🔺)0.987s21.06x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

workflow with 25 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)27.174s (~)28.039s (~)0.865s31.00x
💻 LocalNitro27.470s (~)28.022s (~)0.552s31.01x
💻 LocalExpress27.540s (~)28.029s (~)0.489s31.01x
🐘 PostgresNext.js (Turbopack)37.779s (-25.1% 🟢)38.073s (-25.5% 🟢)0.293s21.39x
🐘 PostgresNitro50.326s (~)51.084s (~)0.758s21.85x
🐘 PostgresExpress50.512s (+34.1% 🔺)51.053s (+34.1% 🔺)0.541s21.86x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express58.465s (+2.0%)59.211s (+2.4%)0.746s21.00x
▲ VercelNitro59.208s (+4.8%)60.393s (+4.9%)1.185s11.01x
▲ VercelNext.js (Turbopack)59.475s (+4.1%)60.388s (+4.7%)0.913s11.02x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)56.673s (~)57.066s (~)0.393s21.00x
💻 LocalNitro57.154s (~)58.043s (~)0.888s21.01x
💻 LocalExpress57.265s (~)58.045s (+0.9%)0.780s21.01x
🐘 PostgresNext.js (Turbopack)74.936s (-23.0% 🟢)75.112s (-23.5% 🟢)0.176s21.32x
🐘 PostgresNitro99.650s (-0.5%)100.121s (-1.0%)0.471s11.76x
🐘 PostgresExpress100.401s (+33.1% 🔺)101.094s (+32.8% 🔺)0.693s11.77x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)142.891s (+14.3% 🔺)143.282s (+13.6% 🔺)0.391s11.00x
▲ VercelNitro144.248s (+19.5% 🔺)145.654s (+19.6% 🔺)1.406s11.01x
▲ VercelExpress144.747s (+17.6% 🔺)145.370s (+16.9% 🔺)0.623s11.01x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.all with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.408s (+2.4%)2.011s (~)0.603s151.00x
💻 LocalExpress1.410s (+0.7%)2.007s (~)0.597s151.00x
💻 LocalNitro1.431s (~)2.006s (~)0.575s151.02x
🐘 PostgresNext.js (Turbopack)1.602s (-31.4% 🟢)2.023s (-33.0% 🟢)0.420s151.14x
🐘 PostgresNitro2.065s (-11.6% 🟢)2.596s (-13.8% 🟢)0.531s121.47x
🐘 PostgresExpress2.371s (~)3.015s (+10.0% 🔺)0.644s101.68x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro2.938s (-0.9%)3.753s (-4.2%)0.815s81.00x
▲ VercelNext.js (Turbopack)3.362s (-6.9% 🟢)4.286s (-0.8%)0.924s81.14x
▲ VercelExpress3.623s (+16.6% 🔺)4.504s (+13.8% 🔺)0.882s81.23x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.all with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.496s (+2.4%)3.030s (~)0.534s101.00x
💻 LocalExpress2.574s (+2.8%)3.017s (~)0.444s101.03x
💻 LocalNitro2.585s (~)3.016s (~)0.431s101.04x
🐘 PostgresExpress8.373s (-27.6% 🟢)8.810s (-24.6% 🟢)0.437s43.35x
🐘 PostgresNitro10.115s (+14.9% 🔺)10.729s (+15.0% 🔺)0.613s34.05x
🐘 PostgresNext.js (Turbopack)10.773s (-11.7% 🟢)11.029s (-13.1% 🟢)0.256s34.32x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.480s (-16.4% 🟢)3.965s (-28.0% 🟢)0.485s81.00x
▲ VercelExpress3.489s (+5.8% 🔺)4.205s (+4.7%)0.717s81.00x
▲ VercelNitro4.271s (-11.4% 🟢)5.095s (-8.7% 🟢)0.825s61.23x

🔍 Observability: Next.js (Turbopack) | Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)6.653s (+0.8%)7.994s (+2.2%)1.342s41.00x
💻 LocalExpress7.504s (+6.5% 🔺)8.490s (+11.5% 🔺)0.986s41.13x
💻 LocalNitro7.518s (-1.0%)8.507s (-0.9%)0.989s41.13x
🐘 PostgresNitro51.285s (+6.4% 🔺)52.142s (+6.1% 🔺)0.857s17.71x
🐘 PostgresExpress51.856s (-1.3%)52.212s (-1.8%)0.356s17.79x
🐘 PostgresNext.js (Turbopack)54.776s (-2.2%)55.208s (-1.7%)0.432s18.23x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Nitro4.285s (-20.6% 🟢)5.328s (-19.3% 🟢)1.043s61.00x
▲ VercelNext.js (Turbopack)4.439s (-21.3% 🟢)5.232s (-19.0% 🟢)0.793s61.04x
▲ VercelExpress4.617s (-20.0% 🟢)5.482s (-16.9% 🟢)0.865s61.08x

🔍 Observability: Nitro | Next.js (Turbopack) | Express

Promise.race with 10 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)1.398s (-4.5%)2.010s (~)0.612s151.00x
💻 LocalExpress1.447s (~)2.007s (~)0.560s151.04x
💻 LocalNitro1.460s (+0.8%)2.007s (~)0.547s151.04x
🐘 PostgresNitro2.133s (-1.8%)2.472s (-12.6% 🟢)0.339s131.53x
🐘 PostgresNext.js (Turbopack)2.174s (-3.9%)2.601s (-5.5% 🟢)0.427s121.55x
🐘 PostgresExpress2.240s (+7.3% 🔺)2.743s (+5.5% 🔺)0.504s111.60x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express2.933s (-7.8% 🟢)3.832s (-2.5%)0.899s81.00x
▲ VercelNitro3.011s (+2.1%)3.969s (+1.5%)0.958s81.03x
▲ VercelNext.js (Turbopack)3.340s (+11.7% 🔺)4.278s (+12.5% 🔺)0.938s81.14x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)2.619s (-3.7%)3.031s (~)0.412s101.00x
💻 LocalNitro2.698s (-4.1%)3.012s (~)0.314s101.03x
💻 LocalExpress2.726s (+3.2%)3.021s (~)0.296s101.04x
🐘 PostgresExpress11.262s (-10.0% 🟢)11.729s (-10.0% 🟢)0.467s34.30x
🐘 PostgresNitro11.775s (-2.9%)12.045s (-5.1% 🟢)0.270s34.50x
🐘 PostgresNext.js (Turbopack)13.458s (-1.7%)14.056s (~)0.597s35.14x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Next.js (Turbopack)3.300s (+1.2%)4.002s (+1.8%)0.701s81.00x
▲ VercelNitro3.430s (+12.9% 🔺)4.120s (+6.7% 🔺)0.690s81.04x
▲ VercelExpress3.464s (+10.2% 🔺)4.134s (+5.9% 🔺)0.670s81.05x

🔍 Observability: Next.js (Turbopack) | Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)7.460s (+5.4% 🔺)8.388s (+8.0% 🔺)0.928s41.00x
💻 LocalNitro7.760s (-0.8%)8.715s (-0.7%)0.955s41.04x
💻 LocalExpress8.046s (+7.5% 🔺)8.940s (+5.4% 🔺)0.894s41.08x
🐘 PostgresNitro52.717s (-2.7%)53.115s (-3.7%)0.398s17.07x
🐘 PostgresExpress53.383s (~)54.294s (~)0.911s17.16x
🐘 PostgresNext.js (Turbopack)55.533s (~)56.227s (~)0.694s17.44x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.623s (-31.5% 🟢)4.035s (-32.1% 🟢)0.412s81.00x
▲ VercelNext.js (Turbopack)3.798s (-58.7% 🟢)4.504s (-54.9% 🟢)0.706s71.05x
▲ VercelNitro3.809s (-50.9% 🟢)4.475s (-46.0% 🟢)0.666s71.05x

🔍 Observability: Express | Next.js (Turbopack) | Nitro

Stream Benchmarks(includes TTFB metrics)
workflow with stream

💻 Local Development

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
💻 Local🥇 Next.js (Turbopack)0.153s (+1.5%)1.003s (~)0.016s (-10.9% 🟢)1.027s (~)0.874s101.00x
💻 LocalExpress0.181s (~)0.993s (~)0.015s (+6.6% 🔺)1.023s (~)0.841s101.19x
💻 LocalNitro0.187s (+2.0%)0.993s (~)0.016s (+11.4% 🔺)1.023s (~)0.836s101.22x
🐘 PostgresNext.js (Turbopack)0.892s (-37.1% 🟢)1.462s (-12.7% 🟢)0.000s (-100.0% 🟢)1.518s (-24.8% 🟢)0.626s105.83x
🐘 PostgresNitro1.325s (-44.2% 🟢)1.715s (-35.7% 🟢)0.000s (-100.0% 🟢)2.014s (-33.2% 🟢)0.689s108.66x
🐘 PostgresExpress2.167s (+96.3% 🔺)2.873s (+48.6% 🔺)0.000s (+Infinity% 🔺)3.014s (+49.6% 🔺)0.847s1014.16x

▲ Production (Vercel)

WorldFrameworkWorkflow TimeTTFBSlurpWall TimeOverheadSamplesvs Fastest
▲ Vercel🥇 Express3.400s (+5.4% 🔺)4.126s (+30.6% 🔺)0.215s (-27.0% 🟢)4.928s (+22.8% 🔺)1.528s101.00x
▲ VercelNitro5.782s (+88.7% 🔺)5.227s (+57.2% 🔺)0.238s (+1.5%)6.679s (+60.9% 🔺)0.897s101.70x
▲ VercelNext.js (Turbopack)6.300s (+98.5% 🔺)5.752s (+76.3% 🔺)0.180s (-70.8% 🟢)7.345s (+65.9% 🔺)1.045s101.85x

🔍 Observability: Express | Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World🥇 Fastest FrameworkWins
💻 LocalNext.js (Turbopack)11/12
🐘 PostgresNext.js (Turbopack)7/12
▲ VercelExpress6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework🥇 Fastest WorldWins
Express💻 Local10/12
Next.js (Turbopack)💻 Local10/12
Nitro💻 Local10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

pranaygpand others added 2 commits February 4, 2026 16:26
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for custom headers in queue messages and includes the x-workflow-run-id header in all workflow and step queue messages for better observability and correlation.

Changes:

  • Updated @vercel/queue dependency from version 0.0.0-alpha.34 to 0.0.0-alpha.36 to enable headers support
  • Added headers field to QueueOptions interface in @workflow/world package
  • Updated @workflow/world-vercel to pass headers through to the VQS client
  • Added x-workflow-run-id header to all queueMessage() calls in step-handler and suspension-handler

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated no comments.

Show a summary per file
FileDescription
pnpm-workspace.yamlUpdates VQS client dependency version to alpha.36
pnpm-lock.yamlUpdates lock file with new VQS client version
packages/world/src/queue.tsAdds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.tsPasses headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.tsIncludes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.tsIncludes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.mdDocuments the change for changelog generation
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Updatednpm/​@​vercel/​queue@​0.0.0-alpha.34 ⏵ 0.0.0-alpha.3698+1100100+198100

View full report

requestedAt: new Date(),
},
{
headers: { 'x-workflow-run-id': workflowRunId },

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

including this so we can log it on the queue server and eventually in sfr/proxy for correlation back to logs

@pranaygp
pranaygp merged commit 0ce46b9 into mainFeb 5, 2026
99 checks passed
@pranaygp
pranaygp deleted the pranaygp/queue-headers branch February 5, 2026 04:34
pranaygp added a commit that referenced this pull request Feb 5, 2026
…-parallelization
* origin/main:
Add x-workflow-run-id header to queue messages (#922)
Bump Next.js and React in workbenches (#944)
Add subpath export resolution for package IDs (#901)
Consolidate console logging to structured logger utility (#935)
# Conflicts:
#	packages/core/src/runtime/step-handler.ts
TooTallNate pushed a commit that referenced this pull request Feb 5, 2026
* Add x-workflow-run-id header to queue messages
Pass the workflow run ID as a custom header when enqueueing messages, enabling better observability and correlation with VQS server logs.
- Add headers field to QueueOptions interface in @workflow/world
- Pass headers through to VQS client in @workflow/world-vercel
- Include x-workflow-run-id header in all queueMessage calls
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Upgrade @vercel/queue to 0.0.0-alpha.36
This version includes the headers support needed for passing x-workflow-run-id to VQS.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Pass custom headers through world-local queue implementation
Custom headers are now spread first in the fetch headers so that system
headers (x-vqs-*, content-type) take precedence and cannot be overridden.
Also adds TODO comment in world-postgres noting headers are not propagated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for freeto 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.

4 participants

@pranaygp@TooTallNate@ctgowrie