Skip to content

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

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

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

Conversation

@pranaygp
Copy link
Copy Markdown
Contributor

@pranaygp pranaygp commented Feb 3, 2026

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
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 3, 2026

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 3, 2026

🦋 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
Name Type
@workflow/world Patch
@workflow/world-vercel Patch
@workflow/world-local Patch
@workflow/core Patch
@workflow/cli Patch
@workflow/web-shared Patch
@workflow/world-postgres Patch
@workflow/world-testing Patch
@workflow/builders Patch
@workflow/docs-typecheck Patch
@workflow/next Patch
@workflow/nitro Patch
workflow Patch
@workflow/astro Patch
@workflow/nest Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/nuxt Patch

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

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 3, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 479 0 38 517
✅ 💻 Local Development 438 0 32 470
✅ 📦 Local Production 438 0 32 470
✅ 🐘 Local Postgres 438 0 32 470
✅ 🪟 Windows 47 0 0 47
❌ 🌍 Community Worlds 31 169 0 200
✅ 📋 Other 129 0 12 141
Total 2000 169 146 2315

❌ 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
App Passed Failed Skipped
✅ astro 43 0 4
✅ example 43 0 4
✅ express 43 0 4
✅ fastify 43 0 4
✅ hono 43 0 4
✅ nextjs-turbopack 46 0 1
✅ nextjs-webpack 46 0 1
✅ nitro 43 0 4
✅ nuxt 43 0 4
✅ sveltekit 43 0 4
✅ vite 43 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 47 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 42 0
✅ redis-dev 3 0 0
❌ redis 5 42 0
✅ starter-dev 3 0 0
❌ starter 4 43 0
✅ turso-dev 3 0 0
❌ turso 5 42 0
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 43 0 4
✅ e2e-local-postgres-nest-stable 43 0 4
✅ e2e-local-prod-nest-stable 43 0 4

📋 View full workflow run

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 3, 2026

📊 Benchmark Results

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

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 0.042s (-3.7%) 1.007s (~) 0.965s 10 1.00x
💻 Local Next.js (Turbopack) 0.043s (+7.8% 🔺) 1.020s (~) 0.977s 10 1.03x
💻 Local Express 0.043s (+1.2%) 1.008s (~) 0.965s 10 1.05x
🐘 Postgres Next.js (Turbopack) 0.111s (-69.6% 🟢) 1.022s (~) 0.911s 10 2.66x
🐘 Postgres Nitro 0.176s (+20.8% 🔺) 1.015s (-0.8%) 0.838s 10 4.24x
🐘 Postgres Express 0.289s (+16.2% 🔺) 1.013s (~) 0.724s 10 6.95x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.650s (-5.4% 🟢) 1.660s (+5.3% 🔺) 1.010s 10 1.00x
▲ Vercel Nitro 0.653s (-4.6%) 1.606s (-7.3% 🟢) 0.952s 10 1.01x
▲ Vercel Next.js (Turbopack) 0.709s (+7.1% 🔺) 1.668s (-16.8% 🟢) 0.959s 10 1.09x

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

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.090s (~) 2.013s (~) 0.923s 10 1.00x
💻 Local Nitro 1.114s (~) 2.007s (~) 0.893s 10 1.02x
💻 Local Express 1.118s (~) 2.009s (~) 0.891s 10 1.03x
🐘 Postgres Next.js (Turbopack) 1.870s (-13.0% 🟢) 2.020s (-33.1% 🟢) 0.150s 10 1.72x
🐘 Postgres Express 2.154s (+13.9% 🔺) 3.013s (+49.6% 🔺) 0.859s 10 1.98x
🐘 Postgres Nitro 2.370s (-4.9%) 3.014s (~) 0.645s 10 2.17x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.785s (-7.7% 🟢) 3.741s (-1.8%) 0.956s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.865s (-0.9%) 3.699s (+1.7%) 0.834s 10 1.03x
▲ Vercel Nitro 2.878s (+1.1%) 3.665s (-5.9% 🟢) 0.787s 10 1.03x

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

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.716s (~) 11.016s (~) 0.299s 3 1.00x
💻 Local Nitro 10.824s (~) 11.015s (~) 0.191s 3 1.01x
💻 Local Express 10.832s (~) 11.017s (~) 0.185s 3 1.01x
🐘 Postgres Next.js (Turbopack) 15.202s (-25.8% 🟢) 16.041s (-23.8% 🟢) 0.839s 2 1.42x
🐘 Postgres Express 20.293s (+32.7% 🔺) 21.030s (+31.2% 🔺) 0.737s 2 1.89x
🐘 Postgres Nitro 20.423s (~) 21.028s (~) 0.605s 2 1.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 22.872s (+1.6%) 23.580s (+0.8%) 0.708s 2 1.00x
▲ Vercel Nitro 23.319s (+3.7%) 24.085s (+4.5%) 0.766s 2 1.02x
▲ Vercel Express 24.172s (+4.7%) 25.160s (+5.8% 🔺) 0.987s 2 1.06x

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

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.174s (~) 28.039s (~) 0.865s 3 1.00x
💻 Local Nitro 27.470s (~) 28.022s (~) 0.552s 3 1.01x
💻 Local Express 27.540s (~) 28.029s (~) 0.489s 3 1.01x
🐘 Postgres Next.js (Turbopack) 37.779s (-25.1% 🟢) 38.073s (-25.5% 🟢) 0.293s 2 1.39x
🐘 Postgres Nitro 50.326s (~) 51.084s (~) 0.758s 2 1.85x
🐘 Postgres Express 50.512s (+34.1% 🔺) 51.053s (+34.1% 🔺) 0.541s 2 1.86x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 58.465s (+2.0%) 59.211s (+2.4%) 0.746s 2 1.00x
▲ Vercel Nitro 59.208s (+4.8%) 60.393s (+4.9%) 1.185s 1 1.01x
▲ Vercel Next.js (Turbopack) 59.475s (+4.1%) 60.388s (+4.7%) 0.913s 1 1.02x

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

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.673s (~) 57.066s (~) 0.393s 2 1.00x
💻 Local Nitro 57.154s (~) 58.043s (~) 0.888s 2 1.01x
💻 Local Express 57.265s (~) 58.045s (+0.9%) 0.780s 2 1.01x
🐘 Postgres Next.js (Turbopack) 74.936s (-23.0% 🟢) 75.112s (-23.5% 🟢) 0.176s 2 1.32x
🐘 Postgres Nitro 99.650s (-0.5%) 100.121s (-1.0%) 0.471s 1 1.76x
🐘 Postgres Express 100.401s (+33.1% 🔺) 101.094s (+32.8% 🔺) 0.693s 1 1.77x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 142.891s (+14.3% 🔺) 143.282s (+13.6% 🔺) 0.391s 1 1.00x
▲ Vercel Nitro 144.248s (+19.5% 🔺) 145.654s (+19.6% 🔺) 1.406s 1 1.01x
▲ Vercel Express 144.747s (+17.6% 🔺) 145.370s (+16.9% 🔺) 0.623s 1 1.01x

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

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.408s (+2.4%) 2.011s (~) 0.603s 15 1.00x
💻 Local Express 1.410s (+0.7%) 2.007s (~) 0.597s 15 1.00x
💻 Local Nitro 1.431s (~) 2.006s (~) 0.575s 15 1.02x
🐘 Postgres Next.js (Turbopack) 1.602s (-31.4% 🟢) 2.023s (-33.0% 🟢) 0.420s 15 1.14x
🐘 Postgres Nitro 2.065s (-11.6% 🟢) 2.596s (-13.8% 🟢) 0.531s 12 1.47x
🐘 Postgres Express 2.371s (~) 3.015s (+10.0% 🔺) 0.644s 10 1.68x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.938s (-0.9%) 3.753s (-4.2%) 0.815s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.362s (-6.9% 🟢) 4.286s (-0.8%) 0.924s 8 1.14x
▲ Vercel Express 3.623s (+16.6% 🔺) 4.504s (+13.8% 🔺) 0.882s 8 1.23x

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

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.496s (+2.4%) 3.030s (~) 0.534s 10 1.00x
💻 Local Express 2.574s (+2.8%) 3.017s (~) 0.444s 10 1.03x
💻 Local Nitro 2.585s (~) 3.016s (~) 0.431s 10 1.04x
🐘 Postgres Express 8.373s (-27.6% 🟢) 8.810s (-24.6% 🟢) 0.437s 4 3.35x
🐘 Postgres Nitro 10.115s (+14.9% 🔺) 10.729s (+15.0% 🔺) 0.613s 3 4.05x
🐘 Postgres Next.js (Turbopack) 10.773s (-11.7% 🟢) 11.029s (-13.1% 🟢) 0.256s 3 4.32x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.480s (-16.4% 🟢) 3.965s (-28.0% 🟢) 0.485s 8 1.00x
▲ Vercel Express 3.489s (+5.8% 🔺) 4.205s (+4.7%) 0.717s 8 1.00x
▲ Vercel Nitro 4.271s (-11.4% 🟢) 5.095s (-8.7% 🟢) 0.825s 6 1.23x

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

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 6.653s (+0.8%) 7.994s (+2.2%) 1.342s 4 1.00x
💻 Local Express 7.504s (+6.5% 🔺) 8.490s (+11.5% 🔺) 0.986s 4 1.13x
💻 Local Nitro 7.518s (-1.0%) 8.507s (-0.9%) 0.989s 4 1.13x
🐘 Postgres Nitro 51.285s (+6.4% 🔺) 52.142s (+6.1% 🔺) 0.857s 1 7.71x
🐘 Postgres Express 51.856s (-1.3%) 52.212s (-1.8%) 0.356s 1 7.79x
🐘 Postgres Next.js (Turbopack) 54.776s (-2.2%) 55.208s (-1.7%) 0.432s 1 8.23x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 4.285s (-20.6% 🟢) 5.328s (-19.3% 🟢) 1.043s 6 1.00x
▲ Vercel Next.js (Turbopack) 4.439s (-21.3% 🟢) 5.232s (-19.0% 🟢) 0.793s 6 1.04x
▲ Vercel Express 4.617s (-20.0% 🟢) 5.482s (-16.9% 🟢) 0.865s 6 1.08x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.398s (-4.5%) 2.010s (~) 0.612s 15 1.00x
💻 Local Express 1.447s (~) 2.007s (~) 0.560s 15 1.04x
💻 Local Nitro 1.460s (+0.8%) 2.007s (~) 0.547s 15 1.04x
🐘 Postgres Nitro 2.133s (-1.8%) 2.472s (-12.6% 🟢) 0.339s 13 1.53x
🐘 Postgres Next.js (Turbopack) 2.174s (-3.9%) 2.601s (-5.5% 🟢) 0.427s 12 1.55x
🐘 Postgres Express 2.240s (+7.3% 🔺) 2.743s (+5.5% 🔺) 0.504s 11 1.60x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.933s (-7.8% 🟢) 3.832s (-2.5%) 0.899s 8 1.00x
▲ Vercel Nitro 3.011s (+2.1%) 3.969s (+1.5%) 0.958s 8 1.03x
▲ Vercel Next.js (Turbopack) 3.340s (+11.7% 🔺) 4.278s (+12.5% 🔺) 0.938s 8 1.14x

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

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.619s (-3.7%) 3.031s (~) 0.412s 10 1.00x
💻 Local Nitro 2.698s (-4.1%) 3.012s (~) 0.314s 10 1.03x
💻 Local Express 2.726s (+3.2%) 3.021s (~) 0.296s 10 1.04x
🐘 Postgres Express 11.262s (-10.0% 🟢) 11.729s (-10.0% 🟢) 0.467s 3 4.30x
🐘 Postgres Nitro 11.775s (-2.9%) 12.045s (-5.1% 🟢) 0.270s 3 4.50x
🐘 Postgres Next.js (Turbopack) 13.458s (-1.7%) 14.056s (~) 0.597s 3 5.14x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.300s (+1.2%) 4.002s (+1.8%) 0.701s 8 1.00x
▲ Vercel Nitro 3.430s (+12.9% 🔺) 4.120s (+6.7% 🔺) 0.690s 8 1.04x
▲ Vercel Express 3.464s (+10.2% 🔺) 4.134s (+5.9% 🔺) 0.670s 8 1.05x

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

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 7.460s (+5.4% 🔺) 8.388s (+8.0% 🔺) 0.928s 4 1.00x
💻 Local Nitro 7.760s (-0.8%) 8.715s (-0.7%) 0.955s 4 1.04x
💻 Local Express 8.046s (+7.5% 🔺) 8.940s (+5.4% 🔺) 0.894s 4 1.08x
🐘 Postgres Nitro 52.717s (-2.7%) 53.115s (-3.7%) 0.398s 1 7.07x
🐘 Postgres Express 53.383s (~) 54.294s (~) 0.911s 1 7.16x
🐘 Postgres Next.js (Turbopack) 55.533s (~) 56.227s (~) 0.694s 1 7.44x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.623s (-31.5% 🟢) 4.035s (-32.1% 🟢) 0.412s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.798s (-58.7% 🟢) 4.504s (-54.9% 🟢) 0.706s 7 1.05x
▲ Vercel Nitro 3.809s (-50.9% 🟢) 4.475s (-46.0% 🟢) 0.666s 7 1.05x

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

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.153s (+1.5%) 1.003s (~) 0.016s (-10.9% 🟢) 1.027s (~) 0.874s 10 1.00x
💻 Local Express 0.181s (~) 0.993s (~) 0.015s (+6.6% 🔺) 1.023s (~) 0.841s 10 1.19x
💻 Local Nitro 0.187s (+2.0%) 0.993s (~) 0.016s (+11.4% 🔺) 1.023s (~) 0.836s 10 1.22x
🐘 Postgres Next.js (Turbopack) 0.892s (-37.1% 🟢) 1.462s (-12.7% 🟢) 0.000s (-100.0% 🟢) 1.518s (-24.8% 🟢) 0.626s 10 5.83x
🐘 Postgres Nitro 1.325s (-44.2% 🟢) 1.715s (-35.7% 🟢) 0.000s (-100.0% 🟢) 2.014s (-33.2% 🟢) 0.689s 10 8.66x
🐘 Postgres Express 2.167s (+96.3% 🔺) 2.873s (+48.6% 🔺) 0.000s (+Infinity% 🔺) 3.014s (+49.6% 🔺) 0.847s 10 14.16x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.400s (+5.4% 🔺) 4.126s (+30.6% 🔺) 0.215s (-27.0% 🟢) 4.928s (+22.8% 🔺) 1.528s 10 1.00x
▲ Vercel Nitro 5.782s (+88.7% 🔺) 5.227s (+57.2% 🔺) 0.238s (+1.5%) 6.679s (+60.9% 🔺) 0.897s 10 1.70x
▲ Vercel Next.js (Turbopack) 6.300s (+98.5% 🔺) 5.752s (+76.3% 🔺) 0.180s (-70.8% 🟢) 7.345s (+65.9% 🔺) 1.045s 10 1.85x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 11/12
🐘 Postgres Next.js (Turbopack) 7/12
▲ Vercel Express 6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 💻 Local 10/12
Nitro 💻 Local 10/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

pranaygp and 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>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

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
File Description
pnpm-workspace.yaml Updates VQS client dependency version to alpha.36
pnpm-lock.yaml Updates lock file with new VQS client version
packages/world/src/queue.ts Adds optional headers field to QueueOptions interface
packages/world-vercel/src/queue.ts Passes headers option through to VQS client's send method
packages/core/src/runtime/suspension-handler.ts Includes x-workflow-run-id header when queueing step messages
packages/core/src/runtime/step-handler.ts Includes x-workflow-run-id header when queueing workflow messages
.changeset/add-queue-headers-support.md Documents 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.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
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
Contributor Author

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 requested a review from TooTallNate February 5, 2026 01:14
@pranaygp pranaygp merged commit 0ce46b9 into main Feb 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 free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants