Skip to content

Conversation

@karthikscale3
Copy link
Collaborator

PR Title

Fix workflow runtime error normalization to avoid [object Promise] and preserve provider failure context

Summary

  • Adds native normalization for unknown thrown values in @workflow/core, including Promise/thenable throw/rejection cases.
  • Replaces string coercion paths (that produced [object Promise]) with structured normalized errors in step/runtime failure handling.
  • Ensures retry/final failure events and logs include meaningful message/stack so provider errors (for example AI Gateway/Veo failures) remain readable and diagnosable.

Why

Workflow retries were ending with opaque errors like failed after 3 retries: [object Promise], which masked the actual provider failure reason and made o11y/debugging difficult.

What changed (workflow package)

  • packages/core/src/types.ts
    • Introduced normalizeUnknownError(...) (async) to normalize:
      • native Error
      • string/non-error values
      • Promise/thenable thrown values and rejections
  • packages/core/src/runtime/step-handler.ts
    • Uses normalized error output for step_retrying and step_failed event payloads/messages.
  • packages/core/src/runtime.ts
    • Uses normalized error output for run_failed workflow-level failures.

Behavior before vs after

  • Before: retry exhaustion could surface [object Promise].
  • After: retry exhaustion surfaces concrete provider/system error details (message + stack), improving API error propagation and telemetry clarity.

Test plan

  • Run a workflow step that throws/rejects with a Promise-like value and verify no [object Promise] appears.
  • Trigger a provider failure (for example blocked Veo prompt) and verify retry/final failure message includes real provider details.
  • Verify step_retrying, step_failed, and run_failed events contain normalized error fields.
  • Confirm no regression for standard Error throws in successful retry/failure flows.

@changeset-bot
Copy link

changeset-bot bot commented Feb 10, 2026

🦋 Changeset detected

Latest commit: c345c9a

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

This PR includes changesets to release 14 packages
Name Type
@workflow/core Patch
@workflow/builders Patch
@workflow/cli Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/web-shared Patch
workflow Patch
@workflow/astro Patch
@workflow/nest Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/world-testing Patch
@workflow/nuxt Patch

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

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

@vercel
Copy link
Contributor

vercel bot commented Feb 10, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Feb 10, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 490 0 38 528
✅ 💻 Local Development 418 0 62 480
✅ 📦 Local Production 418 0 62 480
✅ 🐘 Local Postgres 418 0 62 480
✅ 🪟 Windows 45 0 3 48
❌ 🌍 Community Worlds 106 41 9 156
✅ 📋 Other 123 0 21 144
Total 2018 41 257 2316

❌ Failed Tests

🌍 Community Worlds (41 failed)

turso (41 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • 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 (queue-based) - workflow and step endpoints respond to health check messages
  • 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
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument
  • 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 44 0 4
✅ example 44 0 4
✅ express 44 0 4
✅ fastify 44 0 4
✅ hono 44 0 4
✅ nextjs-turbopack 47 0 1
✅ nextjs-webpack 47 0 1
✅ nitro 44 0 4
✅ nuxt 44 0 4
✅ sveltekit 44 0 4
✅ vite 44 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 41 0 7
✅ express-stable 41 0 7
✅ fastify-stable 41 0 7
✅ hono-stable 41 0 7
✅ nextjs-turbopack-stable 45 0 3
✅ nextjs-webpack-stable 45 0 3
✅ nitro-stable 41 0 7
✅ nuxt-stable 41 0 7
✅ sveltekit-stable 41 0 7
✅ vite-stable 41 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 45 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
✅ mongodb 45 0 3
✅ redis-dev 3 0 0
✅ redis 45 0 3
✅ starter-dev 3 0 0
✅ turso-dev 3 0 0
❌ turso 4 41 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 41 0 7
✅ e2e-local-postgres-nest-stable 41 0 7
✅ e2e-local-prod-nest-stable 41 0 7

📋 View full workflow run

@github-actions
Copy link
Contributor

github-actions bot commented Feb 10, 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.031s (-7.2% 🟢) 1.004s (~) 0.973s 10 1.00x
💻 Local Express 0.032s (+17.6% 🔺) 1.005s (~) 0.973s 10 1.03x
💻 Local Next.js (Turbopack) 0.040s 1.005s 0.965s 10 1.28x
🌐 Redis Next.js (Turbopack) 0.046s 1.004s 0.958s 10 1.48x
🌐 MongoDB Next.js (Turbopack) 0.072s 1.007s 0.935s 10 2.33x
🐘 Postgres Express 0.159s (-33.9% 🟢) 1.009s (~) 0.850s 10 5.14x
🐘 Postgres Nitro 0.266s (-25.4% 🟢) 1.009s (-0.5%) 0.743s 10 8.58x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 0.813s (-12.2% 🟢) 2.426s (-8.6% 🟢) 1.613s 10 1.00x
▲ Vercel Express 0.856s (+0.8%) 2.687s (+15.0% 🔺) 1.831s 10 1.05x
▲ Vercel Nitro 0.892s (+3.6%) 2.372s (-9.7% 🟢) 1.480s 10 1.10x

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

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.097s 2.005s 0.908s 10 1.00x
💻 Local Nitro 1.101s (~) 2.004s (~) 0.903s 10 1.00x
💻 Local Express 1.106s (+2.4%) 2.006s (~) 0.900s 10 1.01x
🌐 Redis Next.js (Turbopack) 1.106s 2.006s 0.900s 10 1.01x
🌐 MongoDB Next.js (Turbopack) 1.307s 2.007s 0.701s 10 1.19x
🐘 Postgres Nitro 1.649s (-29.7% 🟢) 2.011s (-33.3% 🟢) 0.363s 10 1.50x
🐘 Postgres Express 2.278s (-5.5% 🟢) 3.014s (~) 0.735s 10 2.08x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.779s (~) 3.833s (-6.9% 🟢) 1.054s 10 1.00x
▲ Vercel Express 2.844s (+3.9%) 4.183s (+13.0% 🔺) 1.339s 10 1.02x
▲ Vercel Nitro 3.273s (+18.6% 🔺) 4.268s (+5.0% 🔺) 0.996s 10 1.18x

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

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 10.691s 11.021s 0.329s 3 1.00x
💻 Local Next.js (Turbopack) 10.723s 11.023s 0.300s 3 1.00x
💻 Local Nitro 10.806s (~) 11.020s (~) 0.213s 3 1.01x
💻 Local Express 10.824s (+1.9%) 11.021s (~) 0.197s 3 1.01x
🌐 MongoDB Next.js (Turbopack) 12.187s 13.017s 0.829s 3 1.14x
🐘 Postgres Nitro 15.290s (-20.4% 🟢) 16.043s (-20.0% 🟢) 0.753s 2 1.43x
🐘 Postgres Express 20.401s (+0.7%) 21.055s (~) 0.654s 2 1.91x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 22.863s (+16.5% 🔺) 23.903s (+15.0% 🔺) 1.040s 2 1.00x
▲ Vercel Nitro 23.530s (+20.3% 🔺) 25.056s (+18.5% 🔺) 1.526s 2 1.03x
▲ Vercel Next.js (Turbopack) 26.555s (+26.8% 🔺) 28.447s (+25.4% 🔺) 1.891s 2 1.16x

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

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 26.808s 27.047s 0.239s 3 1.00x
💻 Local Next.js (Turbopack) 27.209s 28.052s 0.843s 3 1.01x
💻 Local Nitro 27.378s (~) 28.049s (~) 0.671s 3 1.02x
💻 Local Express 27.489s (+1.9%) 28.050s (+2.4%) 0.561s 3 1.03x
🌐 MongoDB Next.js (Turbopack) 30.381s 31.041s 0.659s 2 1.13x
🐘 Postgres Nitro 38.114s (-17.1% 🟢) 38.600s (-17.2% 🟢) 0.485s 2 1.42x
🐘 Postgres Express 49.946s (-0.7%) 50.626s (~) 0.680s 2 1.86x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 49.992s (-5.7% 🟢) 51.488s (-5.3% 🟢) 1.496s 2 1.00x
▲ Vercel Express 50.331s (~) 52.001s (+1.6%) 1.670s 2 1.01x
▲ Vercel Nitro 50.527s (-4.1%) 51.310s (-4.9%) 0.783s 2 1.01x

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

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 54.169s 55.094s 0.925s 2 1.00x
💻 Local Next.js (Turbopack) 56.675s 57.100s 0.425s 2 1.05x
💻 Local Nitro 56.936s (~) 57.098s (-0.9%) 0.162s 2 1.05x
💻 Local Express 57.302s (+2.3%) 58.105s (+2.7%) 0.803s 2 1.06x
🌐 MongoDB Next.js (Turbopack) 60.650s 61.065s 0.415s 2 1.12x
🐘 Postgres Nitro 80.232s (-16.5% 🟢) 80.687s (-16.1% 🟢) 0.455s 2 1.48x
🐘 Postgres Express 100.435s (~) 101.231s (+1.0%) 0.796s 1 1.85x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 104.803s (-2.6%) 106.670s (-2.5%) 1.867s 1 1.00x
▲ Vercel Nitro 106.638s (+0.8%) 108.301s (+0.7%) 1.663s 1 1.02x
▲ Vercel Next.js (Turbopack) 117.072s (+9.1% 🔺) 118.235s (+8.5% 🔺) 1.163s 1 1.12x

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

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.254s 2.006s 0.752s 15 1.00x
💻 Local Nitro 1.388s (-2.7%) 2.004s (~) 0.617s 15 1.11x
💻 Local Next.js (Turbopack) 1.404s 2.006s 0.602s 15 1.12x
💻 Local Express 1.420s (+2.9%) 2.005s (~) 0.584s 15 1.13x
🐘 Postgres Nitro 1.976s (-12.7% 🟢) 2.322s (-23.0% 🟢) 0.346s 13 1.58x
🌐 MongoDB Next.js (Turbopack) 2.138s 3.007s 0.869s 10 1.70x
🐘 Postgres Express 2.559s (+15.4% 🔺) 3.013s (~) 0.453s 10 2.04x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.837s (~) 4.175s (+8.3% 🔺) 1.339s 8 1.00x
▲ Vercel Next.js (Turbopack) 3.057s (-9.3% 🟢) 4.046s (-9.6% 🟢) 0.990s 8 1.08x
▲ Vercel Nitro 3.178s (+7.5% 🔺) 4.124s (+1.1%) 0.947s 8 1.12x

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

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 2.478s (-1.5%) 3.007s (~) 0.529s 10 1.00x
🌐 Redis Next.js (Turbopack) 2.495s 3.007s 0.513s 10 1.01x
💻 Local Next.js (Turbopack) 2.579s 3.007s 0.428s 10 1.04x
💻 Local Express 2.608s (+9.7% 🔺) 3.007s (~) 0.399s 10 1.05x
🌐 MongoDB Next.js (Turbopack) 4.704s 5.177s 0.473s 6 1.90x
🐘 Postgres Express 8.668s (+8.5% 🔺) 9.278s (+8.7% 🔺) 0.610s 4 3.50x
🐘 Postgres Nitro 11.157s (+39.0% 🔺) 11.712s (+37.2% 🔺) 0.555s 3 4.50x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.246s (-44.4% 🟢) 4.194s (-50.0% 🟢) 0.948s 8 1.00x
▲ Vercel Nitro 3.263s (-10.1% 🟢) 4.238s (-12.2% 🟢) 0.975s 8 1.01x
▲ Vercel Express 3.272s (~) 4.427s (~) 1.155s 7 1.01x

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

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.044s 4.724s 0.680s 7 1.00x
💻 Local Nitro 7.121s (-3.0%) 7.767s (-3.2%) 0.645s 4 1.76x
💻 Local Next.js (Turbopack) 7.410s 8.014s 0.604s 4 1.83x
💻 Local Express 7.596s (+14.9% 🔺) 8.024s (+14.4% 🔺) 0.428s 4 1.88x
🌐 MongoDB Next.js (Turbopack) 9.866s 10.349s 0.483s 3 2.44x
🐘 Postgres Express 49.236s (-4.0%) 50.119s (-3.9%) 0.883s 1 12.17x
🐘 Postgres Nitro 51.811s (+9.7% 🔺) 52.150s (+8.4% 🔺) 0.339s 1 12.81x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.798s (-44.5% 🟢) 5.032s (-39.6% 🟢) 1.234s 7 1.00x
▲ Vercel Nitro 4.045s (-47.4% 🟢) 5.322s (-41.4% 🟢) 1.277s 6 1.06x
▲ Vercel Next.js (Turbopack) 4.681s (-20.3% 🟢) 6.076s (-22.9% 🟢) 1.395s 5 1.23x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.267s 2.005s 0.739s 15 1.00x
💻 Local Express 1.421s (+3.4%) 2.005s (~) 0.584s 15 1.12x
💻 Local Nitro 1.432s (-2.4%) 2.005s (~) 0.573s 15 1.13x
💻 Local Next.js (Turbopack) 1.442s 2.006s 0.563s 15 1.14x
🐘 Postgres Nitro 1.954s (-14.3% 🟢) 2.321s (-10.6% 🟢) 0.367s 13 1.54x
🐘 Postgres Express 2.116s (~) 2.512s (~) 0.396s 12 1.67x
🌐 MongoDB Next.js (Turbopack) 2.187s 3.007s 0.820s 10 1.73x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.675s (-21.7% 🟢) 4.096s (-8.9% 🟢) 1.421s 8 1.00x
▲ Vercel Nitro 2.715s (-1.6%) 3.713s (-10.6% 🟢) 0.998s 9 1.01x
▲ Vercel Next.js (Turbopack) 2.740s (-6.9% 🟢) 3.783s (-12.5% 🟢) 1.043s 8 1.02x

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

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 2.471s 3.007s 0.536s 10 1.00x
💻 Local Next.js (Turbopack) 2.610s 3.008s 0.398s 10 1.06x
💻 Local Nitro 2.666s (-3.3%) 3.007s (-3.3%) 0.341s 10 1.08x
💻 Local Express 2.699s (+13.0% 🔺) 3.008s (~) 0.308s 10 1.09x
🌐 MongoDB Next.js (Turbopack) 4.596s 5.175s 0.579s 6 1.86x
🐘 Postgres Nitro 9.246s (-27.7% 🟢) 9.779s (-26.9% 🟢) 0.533s 4 3.74x
🐘 Postgres Express 10.989s (+5.1% 🔺) 11.364s (+3.0%) 0.375s 3 4.45x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.964s (-20.4% 🟢) 4.368s (-13.1% 🟢) 1.404s 8 1.00x
▲ Vercel Express 3.099s (+8.5% 🔺) 4.344s (+19.7% 🔺) 1.245s 7 1.05x
▲ Vercel Next.js (Turbopack) 3.318s (-21.5% 🟢) 5.091s (-5.1% 🟢) 1.772s 6 1.12x

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

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.047s 4.581s 0.534s 7 1.00x
💻 Local Nitro 7.475s (-8.3% 🟢) 8.016s (-8.6% 🟢) 0.542s 4 1.85x
💻 Local Next.js (Turbopack) 7.535s 8.266s 0.731s 4 1.86x
💻 Local Express 8.086s (+13.6% 🔺) 8.773s (+9.5% 🔺) 0.687s 4 2.00x
🌐 MongoDB Next.js (Turbopack) 9.723s 10.347s 0.624s 3 2.40x
🐘 Postgres Nitro 48.435s (-7.4% 🟢) 49.124s (-7.5% 🟢) 0.689s 1 11.97x
🐘 Postgres Express 54.701s (+5.4% 🔺) 55.125s (+5.8% 🔺) 0.424s 1 13.52x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.421s (-53.2% 🟢) 4.838s (-44.1% 🟢) 1.417s 7 1.00x
▲ Vercel Nitro 3.509s (-59.7% 🟢) 4.860s (-52.8% 🟢) 1.351s 7 1.03x
▲ Vercel Next.js (Turbopack) 3.744s (-41.2% 🟢) 5.215s (-32.2% 🟢) 1.471s 6 1.09x

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

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.141s 1.001s 0.011s 1.016s 0.875s 10 1.00x
🌐 Redis Next.js (Turbopack) 0.147s 1.000s 0.002s 1.007s 0.860s 10 1.04x
💻 Local Nitro 0.169s (-2.3%) 1.002s (~) 0.010s (~) 1.014s (~) 0.846s 10 1.20x
💻 Local Express 0.172s (+37.2% 🔺) 1.002s (~) 0.010s (+2.1%) 1.015s (~) 0.844s 10 1.22x
🌐 MongoDB Next.js (Turbopack) 0.464s 0.982s 0.001s 1.008s 0.544s 10 3.30x
🐘 Postgres Nitro 1.259s (+1.2%) 1.780s (-0.9%) 0.001s (+18.2% 🔺) 2.013s (~) 0.754s 10 8.95x
🐘 Postgres Express 2.208s (-3.2%) 2.830s (+2.7%) 0.001s (-26.7% 🟢) 3.014s (~) 0.806s 10 15.69x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.479s (-15.5% 🟢) 2.937s (-4.6%) 0.159s (+12.1% 🔺) 3.837s (-9.5% 🟢) 1.358s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.549s (-25.8% 🟢) 3.086s (-18.2% 🟢) 0.096s (-46.9% 🟢) 3.957s (-20.0% 🟢) 1.408s 10 1.03x
▲ Vercel Express 2.624s (+1.0%) 3.204s (+6.5% 🔺) 0.182s (-15.7% 🟢) 4.247s (+6.3% 🔺) 1.624s 10 1.06x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 6/12
🐘 Postgres Nitro 9/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) 🌐 Redis 8/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

expect(result.message).toContain('Step error message');
// Stack trace contains function name and source file
expect(result.stack).toContain('errorStepFn');
// Stack trace can show either the original step function or its transformed wrapper name
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

this test was flaky, so i fixed it as part of this PR - it's unrelated to the changes made in this PR

@karthikscale3 karthikscale3 merged commit fc4cad6 into main Feb 10, 2026
97 of 99 checks passed
@karthikscale3 karthikscale3 deleted the karthik/error-serialization branch February 10, 2026 17:44
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.

2 participants