Skip to content

[core] [world] Lazy run creation on start#1537

Draft
VaguelySerious wants to merge 17 commits intomainfrom
peter/lazy-start
Draft

[core] [world] Lazy run creation on start#1537
VaguelySerious wants to merge 17 commits intomainfrom
peter/lazy-start

Conversation

@VaguelySerious
Copy link
Copy Markdown
Member

@VaguelySerious VaguelySerious commented Mar 27, 2026 •
edited
Loading

This PR:

  • Makes start resilient: ensures that as long as the queue is up, the world storage layer being down will not affect run creations, only defer them
  • Rolls up getting the run, posting run_created, and posting run_started calls into one
    • This saves two server round trips on the first start, reducing TTFB time by up to ~300ms
  • Returns the list of events in the same call when starting the run initially, and forcing server-side ref solution on those events for this case
    • This saves another two server round trips on the first start, reducing TTFB time by up to another ~300ms

See the live docs

TODO:

  • Fix base64 hack for queue roundtrips
  • Fix await getRun UX for 404s

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Mar 27, 2026 •
edited
Loading

🦋 Changeset detected

Latest commit: 7b51efd

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

This PR includes changesets to release 20 packages
Name Type
@workflow/world Patch
@workflow/core Minor
@workflow/world-local Patch
@workflow/world-postgres Patch
@workflow/world-vercel Patch
@workflow/cli Patch
@workflow/vitest Patch
@workflow/web-shared Patch
@workflow/world-testing Patch
@workflow/builders Patch
@workflow/next Patch
@workflow/nitro Patch
workflow Minor
@workflow/astro Patch
@workflow/nest Patch
@workflow/rollup Patch
@workflow/sveltekit Patch
@workflow/vite Patch
@workflow/nuxt Patch
@workflow/ai Major

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

vercel bot commented Mar 27, 2026 •
edited
Loading

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

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Mar 31, 2026 7:55pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Mar 31, 2026 7:55pm
example-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-astro-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-express-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-fastify-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-hono-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-nitro-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-nuxt-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workbench-vite-workflow Ready Ready Preview, Comment Mar 31, 2026 7:55pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Mar 31, 2026 7:55pm
workflow-swc-playground Ready Ready Preview, Comment Mar 31, 2026 7:55pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 27, 2026 •
edited
Loading

📊 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
🌐 Redis 🥇 Next.js (Turbopack) 0.052s (+18.1% 🔺) 1.005s (~) 0.952s 10 1.00x
🐘 Postgres Express 0.058s (-15.9% 🟢) 1.010s (~) 0.952s 10 1.11x
🐘 Postgres Next.js (Turbopack) 0.059s (-12.2% 🟢) 1.009s (~) 0.950s 10 1.13x
🐘 Postgres Nitro 0.064s (-7.9% 🟢) 1.010s (~) 0.946s 10 1.23x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 0.273s (-54.0% 🟢) 2.291s (-7.1% 🟢) 2.017s 10 1.00x
▲ Vercel Nitro 0.302s (-42.3% 🟢) 2.003s (-27.1% 🟢) 1.701s 10 1.11x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.125s (+1.1%) 2.006s (~) 0.881s 10 1.00x
🐘 Postgres Next.js (Turbopack) 1.140s (~) 2.009s (~) 0.869s 10 1.01x
🐘 Postgres Express 1.143s (-0.7%) 2.010s (~) 0.867s 10 1.02x
🐘 Postgres Nitro 1.149s (~) 2.009s (~) 0.860s 10 1.02x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 1.905s (-8.5% 🟢) 3.218s (-17.4% 🟢) 1.313s 10 1.00x
▲ Vercel Next.js (Turbopack) 1.946s (-7.0% 🟢) 3.797s (-2.7%) 1.850s 10 1.02x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 10.759s (+1.6%) 11.022s (~) 0.263s 3 1.00x
🐘 Postgres Next.js (Turbopack) 10.812s (-1.1%) 11.021s (~) 0.209s 3 1.00x
🐘 Postgres Nitro 10.891s (~) 11.017s (~) 0.126s 3 1.01x
🐘 Postgres Express 10.910s (~) 11.021s (~) 0.111s 3 1.01x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 17.242s (-25.1% 🟢) 18.472s (-27.3% 🟢) 1.229s 2 1.00x
▲ Vercel Next.js (Turbopack) 17.640s (+3.3%) 19.736s (+3.1%) 2.096s 2 1.02x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: 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) 14.284s (+2.9%) 15.028s (+5.6% 🔺) 0.744s 4 1.00x
🐘 Postgres Next.js (Turbopack) 14.456s (~) 15.025s (~) 0.569s 4 1.01x
🐘 Postgres Nitro 14.470s (-0.9%) 15.019s (~) 0.548s 4 1.01x
🐘 Postgres Express 14.613s (~) 15.026s (~) 0.413s 4 1.02x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 32.827s (+2.1%) 33.924s (-0.6%) 1.098s 2 1.00x
▲ Vercel Next.js (Turbopack) 34.036s (+2.7%) 35.451s (+1.1%) 1.415s 2 1.04x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 13.403s (+6.3% 🔺) 14.025s (+7.7% 🔺) 0.622s 7 1.00x
🐘 Postgres Nitro 13.929s (-1.2%) 14.449s (-2.0%) 0.520s 7 1.04x
🐘 Postgres Next.js (Turbopack) 13.951s (~) 14.162s (~) 0.212s 7 1.04x
🐘 Postgres Express 14.041s (-2.5%) 14.449s (-3.8%) 0.408s 7 1.05x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 61.010s (+6.0% 🔺) 62.728s (+4.6%) 1.718s 2 1.00x
▲ Vercel Next.js (Turbopack) 66.719s (+11.5% 🔺) 68.642s (+11.5% 🔺) 1.923s 2 1.09x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Next.js (Turbopack) 1.219s (-1.4%) 2.009s (~) 0.790s 15 1.00x
🐘 Postgres Nitro 1.268s (~) 2.009s (~) 0.741s 15 1.04x
🐘 Postgres Express 1.290s (+1.3%) 2.011s (~) 0.721s 15 1.06x
🌐 Redis Next.js (Turbopack) 1.319s (+7.8% 🔺) 2.006s (~) 0.687s 15 1.08x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.179s (-10.6% 🟢) 3.395s (-15.9% 🟢) 1.215s 9 1.00x
▲ Vercel Next.js (Turbopack) 2.522s (-3.1%) 4.169s (+2.6%) 1.648s 8 1.16x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 2.308s (-1.7%) 3.008s (~) 0.700s 10 1.00x
🐘 Postgres Express 2.353s (-0.6%) 3.011s (~) 0.658s 10 1.02x
🐘 Postgres Next.js (Turbopack) 2.373s (-2.8%) 3.010s (~) 0.638s 10 1.03x
🌐 Redis Next.js (Turbopack) 2.529s (+5.1% 🔺) 3.007s (~) 0.479s 10 1.10x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.065s (+7.7% 🔺) 4.504s (+5.6% 🔺) 1.439s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.127s (-14.0% 🟢) 4.722s (-7.3% 🟢) 1.595s 7 1.02x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 3.468s (-0.6%) 4.012s (~) 0.545s 8 1.00x
🐘 Postgres Nitro 3.474s (~) 4.010s (~) 0.537s 8 1.00x
🐘 Postgres Next.js (Turbopack) 3.648s (~) 4.008s (~) 0.360s 8 1.05x
🌐 Redis Next.js (Turbopack) 4.176s (+6.9% 🔺) 5.012s (+21.2% 🔺) 0.835s 6 1.20x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.752s (-9.4% 🟢) 4.302s (-14.9% 🟢) 1.550s 7 1.00x
▲ Vercel Next.js (Turbopack) 3.597s (-5.9% 🟢) 5.622s (-3.9%) 2.025s 6 1.31x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Next.js (Turbopack) 1.220s (-1.2%) 2.008s (~) 0.788s 15 1.00x
🐘 Postgres Express 1.255s (~) 2.007s (~) 0.752s 15 1.03x
🐘 Postgres Nitro 1.266s (~) 2.008s (~) 0.741s 15 1.04x
🌐 Redis Next.js (Turbopack) 1.288s (+4.6%) 2.006s (~) 0.718s 15 1.06x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.213s (-9.6% 🟢) 3.396s (-15.0% 🟢) 1.183s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.269s (-4.2%) 3.959s (-0.8%) 1.690s 8 1.03x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 2.324s (~) 3.008s (~) 0.684s 10 1.00x
🐘 Postgres Nitro 2.333s (-1.0%) 3.010s (~) 0.677s 10 1.00x
🐘 Postgres Next.js (Turbopack) 2.391s (~) 3.008s (~) 0.618s 10 1.03x
🌐 Redis Next.js (Turbopack) 2.547s (+5.5% 🔺) 3.008s (~) 0.461s 10 1.10x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.520s (-19.1% 🟢) 3.916s (-16.3% 🟢) 1.396s 8 1.00x
▲ Vercel Nitro 3.316s (+14.5% 🔺) 4.485s (+4.0%) 1.169s 7 1.32x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 3.462s (-0.6%) 4.011s (~) 0.549s 8 1.00x
🐘 Postgres Nitro 3.467s (-0.9%) 4.009s (~) 0.542s 8 1.00x
🐘 Postgres Next.js (Turbopack) 3.621s (-1.8%) 4.011s (~) 0.390s 8 1.05x
🌐 Redis Next.js (Turbopack) 4.139s (+5.7% 🔺) 4.725s (+6.4% 🔺) 0.586s 7 1.20x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.952s (-11.5% 🟢) 4.506s (-6.1% 🟢) 1.554s 7 1.00x
▲ Vercel Next.js (Turbopack) 4.573s (+20.3% 🔺) 6.187s (+8.7% 🔺) 1.614s 5 1.55x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 10 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 0.685s (+19.6% 🔺) 1.004s (-1.7%) 0.319s 60 1.00x
🐘 Postgres Next.js (Turbopack) 0.767s (-4.9%) 1.040s (+3.2%) 0.274s 58 1.12x
🐘 Postgres Express 0.807s (-4.1%) 1.005s (~) 0.199s 60 1.18x
🐘 Postgres Nitro 0.904s (+7.0% 🔺) 1.058s (+5.1% 🔺) 0.154s 57 1.32x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 10.517s (-7.8% 🟢) 12.779s (-4.8%) 2.262s 5 1.00x
▲ Vercel Nitro 10.680s (+4.1%) 12.038s (-1.7%) 1.357s 5 1.02x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Next.js (Turbopack) | Nitro

workflow with 25 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.618s (+24.9% 🔺) 2.006s (~) 0.387s 45 1.00x
🐘 Postgres Next.js (Turbopack) 1.874s (-4.8%) 2.100s (-7.0% 🟢) 0.226s 43 1.16x
🐘 Postgres Express 1.924s (-4.8%) 2.100s (-20.4% 🟢) 0.175s 43 1.19x
🐘 Postgres Nitro 2.051s (+1.0%) 2.401s (-11.6% 🟢) 0.351s 38 1.27x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 32.868s (-4.1%) 34.407s (-5.2% 🟢) 1.539s 3 1.00x
▲ Vercel Next.js (Turbopack) 35.458s (+3.3%) 37.679s (+4.6%) 2.221s 3 1.08x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 50 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 3.277s (+25.1% 🔺) 4.008s (+31.1% 🔺) 0.731s 30 1.00x
🐘 Postgres Next.js (Turbopack) 3.797s (-3.4%) 4.042s (-4.9%) 0.245s 30 1.16x
🐘 Postgres Express 3.924s (-4.9%) 4.182s (-13.8% 🟢) 0.258s 29 1.20x
🐘 Postgres Nitro 3.971s (-3.2%) 4.403s (-8.5% 🟢) 0.432s 28 1.21x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 98.805s (+12.6% 🔺) 100.252s (+11.7% 🔺) 1.447s 2 1.00x
▲ Vercel Next.js (Turbopack) 99.024s (+7.5% 🔺) 100.637s (+7.2% 🔺) 1.613s 2 1.00x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 10 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Next.js (Turbopack) 0.243s (-7.7% 🟢) 1.007s (~) 0.764s 60 1.00x
🌐 Redis Next.js (Turbopack) 0.275s (+3.4%) 1.004s (~) 0.729s 60 1.13x
🐘 Postgres Express 0.278s (-5.9% 🟢) 1.006s (~) 0.728s 60 1.15x
🐘 Postgres Nitro 0.285s (-3.7%) 1.006s (~) 0.722s 60 1.17x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 1.711s (+1.3%) 3.188s (-6.2% 🟢) 1.478s 19 1.00x
▲ Vercel Next.js (Turbopack) 1.893s (-5.5% 🟢) 3.764s (+2.8%) 1.871s 16 1.11x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 25 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Next.js (Turbopack) 0.470s (-5.9% 🟢) 1.006s (~) 0.536s 90 1.00x
🐘 Postgres Nitro 0.492s (-4.6%) 1.006s (~) 0.514s 90 1.05x
🐘 Postgres Express 0.494s (-5.7% 🟢) 1.007s (~) 0.513s 90 1.05x
🌐 Redis Next.js (Turbopack) 1.132s (+4.9%) 2.005s (+7.7% 🔺) 0.874s 45 2.41x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.074s (-24.3% 🟢) 4.660s (-17.5% 🟢) 1.586s 20 1.00x
▲ Vercel Next.js (Turbopack) 3.440s (-93.9% 🟢) 5.276s (-90.9% 🟢) 1.836s 18 1.12x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

workflow with 50 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Next.js (Turbopack) 0.744s (-2.8%) 1.006s (~) 0.262s 120 1.00x
🐘 Postgres Nitro 0.791s (-1.4%) 1.008s (~) 0.216s 120 1.06x
🐘 Postgres Express 0.835s (+1.6%) 1.044s (+3.3%) 0.209s 115 1.12x
🌐 Redis Next.js (Turbopack) 2.629s (+1.4%) 3.007s (~) 0.377s 40 3.53x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 6.413s (-18.7% 🟢) 8.311s (-13.6% 🟢) 1.898s 15 1.00x
▲ Vercel Nitro 9.960s (+20.5% 🔺) 11.280s (+11.5% 🔺) 1.320s 11 1.55x
▲ Vercel Express ⚠️ missing - - - -

🔍 Observability: 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
🌐 Redis 🥇 Next.js (Turbopack) 0.181s (+28.4% 🔺) 1.001s (~) 0.002s (+46.2% 🔺) 1.007s (~) 0.827s 10 1.00x
🐘 Postgres Next.js (Turbopack) 0.189s (-4.9%) 1.001s (~) 0.001s (+8.3% 🔺) 1.009s (~) 0.820s 10 1.05x
🐘 Postgres Express 0.206s (-6.7% 🟢) 0.994s (~) 0.001s (~) 1.010s (~) 0.804s 10 1.14x
🐘 Postgres Nitro 0.218s (+2.5%) 0.996s (~) 0.001s (-8.3% 🟢) 1.008s (~) 0.790s 10 1.20x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 1.461s (-12.0% 🟢) 2.921s (+1.7%) 0.340s (-39.3% 🟢) 3.597s (-12.4% 🟢) 2.136s 10 1.00x
▲ Vercel Next.js (Turbopack) 1.485s (-10.8% 🟢) 2.963s (+4.1%) 0.427s (-31.3% 🟢) 3.820s (-8.2% 🟢) 2.335s 10 1.02x
▲ Vercel Express ⚠️ missing - - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

stream pipeline with 5 transform steps (1MB)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 0.477s (+25.7% 🔺) 1.001s (~) 0.003s (-6.7% 🟢) 1.009s (~) 0.532s 60 1.00x
🐘 Postgres Next.js (Turbopack) 0.597s (-2.5%) 1.008s (~) 0.006s (+48.7% 🔺) 1.023s (~) 0.425s 59 1.25x
🐘 Postgres Nitro 0.613s (-1.7%) 1.002s (~) 0.005s (+11.5% 🔺) 1.023s (~) 0.410s 59 1.28x
🐘 Postgres Express 0.655s (+5.2% 🔺) 1.006s (~) 0.004s (~) 1.024s (~) 0.370s 59 1.37x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 4.878s (+18.0% 🔺) 5.749s (+7.8% 🔺) 0.227s (-3.9%) 6.350s (+1.1%) 1.473s 10 1.00x
▲ Vercel Next.js (Turbopack) 5.560s (-8.6% 🟢) 6.798s (-11.4% 🟢) 0.251s (+9.9% 🔺) 7.940s (-7.9% 🟢) 2.380s 8 1.14x
▲ Vercel Express ⚠️ missing - - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

10 parallel streams (1MB each)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 0.896s (+6.6% 🔺) 1.034s (+3.5%) 0.000s (+55.2% 🔺) 1.038s (+3.4%) 0.143s 58 1.00x
🐘 Postgres Next.js (Turbopack) 0.921s (-6.0% 🟢) 1.155s (-11.5% 🟢) 0.000s (+76.9% 🔺) 1.162s (-11.6% 🟢) 0.241s 52 1.03x
🐘 Postgres Nitro 0.963s (-3.8%) 1.169s (-13.7% 🟢) 0.000s (-56.9% 🟢) 1.184s (-14.2% 🟢) 0.221s 51 1.08x
🐘 Postgres Express 0.992s (+2.5%) 1.271s (+3.9%) 0.000s (-100.0% 🟢) 1.285s (+2.7%) 0.293s 47 1.11x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.794s (-16.8% 🟢) 3.964s (-7.7% 🟢) 0.000s (+Infinity% 🔺) 4.286s (-14.4% 🟢) 1.491s 15 1.00x
▲ Vercel Next.js (Turbopack) 3.921s (+24.2% 🔺) 4.905s (+14.1% 🔺) 0.000s (-100.0% 🟢) 5.546s (+12.2% 🔺) 1.625s 11 1.40x
▲ Vercel Express ⚠️ missing - - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

fan-out fan-in 10 streams (1MB each)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.560s (+0.6%) 2.002s (-1.6%) 0.000s (~) 2.006s (-1.6%) 0.446s 30 1.00x
🐘 Postgres Express 1.732s (-2.5%) 2.102s (-0.9%) 0.000s (+Infinity% 🔺) 2.113s (-2.4%) 0.381s 29 1.11x
🐘 Postgres Next.js (Turbopack) 1.783s (-6.9% 🟢) 2.106s (-1.8%) 0.000s (-3.4%) 2.119s (-1.6%) 0.336s 29 1.14x
🐘 Postgres Nitro 1.784s (-0.5%) 2.135s (~) 0.000s (-100.0% 🟢) 2.148s (~) 0.364s 29 1.14x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.669s (-20.2% 🟢) 4.759s (-15.4% 🟢) 0.000s (+66.7% 🔺) 5.123s (-18.7% 🟢) 1.454s 12 1.00x
▲ Vercel Next.js (Turbopack) 4.037s (-15.5% 🟢) 5.442s (-7.7% 🟢) 0.000s (-54.5% 🟢) 5.861s (-11.3% 🟢) 1.824s 11 1.10x
▲ Vercel Express ⚠️ missing - - - - -

🔍 Observability: Nitro | Next.js (Turbopack)

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
🐘 Postgres Next.js (Turbopack) 14/21
▲ Vercel Nitro 17/21
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 🐘 Postgres 21/21
Next.js (Turbopack) 🌐 Redis 12/21
Nitro 🐘 Postgres 19/21
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
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run

❌ Some benchmark jobs failed:

  • Local: failure
  • Postgres: success
  • Vercel: failure

Check the workflow run for details.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 27, 2026 •
edited
Loading

🧪 E2E Test Results

❌ Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 868 0 67 935
❌ 💻 Local Development 841 1 178 1020
❌ 📦 Local Production 839 3 178 1020
✅ 🐘 Local Postgres 842 0 178 1020
✅ 🪟 Windows 77 0 8 85
❌ 🌍 Community Worlds 132 63 24 219
✅ 📋 Other 213 0 42 255
Total 3812 67 675 4554

❌ Failed Tests

💻 Local Development (1 failed)

nitro-stable (1 failed):

  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KN2QEKCFV7MV9B8KA8M539AR
📦 Local Production (3 failed)

nitro-stable (1 failed):

  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KN2QQ72C941HRMMY8JX1TVMV

nuxt-stable (1 failed):

  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KN2QNXCQR0JQGS7T8ZXFSF07

sveltekit-stable (1 failed):

  • DurableAgent e2e core tool error recovery
🌍 Community Worlds (63 failed)

mongodb (4 failed):

  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KN2QEKCFV7MV9B8KA8M539AR
  • webhookWorkflow | wrun_01KN2QEW668W4V97TP89D05SAB
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KN2QPHNK23Q1YY0NQYCE7K80
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KN2QWVTVE669536H42XNSC3Y

redis (3 failed):

  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KN2QEKCFV7MV9B8KA8M539AR
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KN2QPHNK23Q1YY0NQYCE7K80
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KN2QWVTVE669536H42XNSC3Y

turso (56 failed):

  • addTenWorkflow | wrun_01KN2QDDSSSS6C19C5G4A24XRH
  • addTenWorkflow | wrun_01KN2QDDSSSS6C19C5G4A24XRH
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KN2QEPH2W5N3G54MGQ9WXACD
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KN2QDMCX6ZB60Y45EXGZD66S
  • promiseRaceWorkflow | wrun_01KN2QDRQ33P3RG5KY08A2A11X
  • promiseAnyWorkflow | wrun_01KN2QDTWWGFS024K1E2NX7HZ2
  • importedStepOnlyWorkflow | wrun_01KN2QF22SEQPB0W7JT88J703D
  • hookWorkflow | wrun_01KN2QE8KQ94APDRYD8HKZ41XQ
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KN2QEKCFV7MV9B8KA8M539AR
  • webhookWorkflow | wrun_01KN2QEW668W4V97TP89D05SAB
  • sleepingWorkflow | wrun_01KN2QF3XFJN4PH1VHM3Z4R1KK
  • parallelSleepWorkflow | wrun_01KN2QFGNTJR01DR2H9BWG179J
  • nullByteWorkflow | wrun_01KN2QFKVBGVB2FSS3RPQR7QYZ
  • workflowAndStepMetadataWorkflow | wrun_01KN2QFPJP12TQB23RMPZTP8JT
  • fetchWorkflow | wrun_01KN2QJC6NWV8T9HE3SRCN91ZW
  • promiseRaceStressTestWorkflow | wrun_01KN2QJEVPP88B73ET4DEB11DE
  • 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()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KN2QNXCQR0JQGS7T8ZXFSF07
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KN2QPHNK23Q1YY0NQYCE7K80
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KN2QQ72C941HRMMY8JX1TVMV
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KN2QQTENQS1DCXBW97CB6YK8
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KN2QR3R2DSFCX3V7JBAQF95X
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KN2QR93ETMMZB5JEPEGBF1Q8
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KN2QRB3A4M8P74ZNRKYG6NJC
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KN2QRT0XWE5TSVWAJ3JVJ6TD
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KN2QRZPBXHQQZHWRY1CK81J5
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KN2QS681YMBC13TQDWFCQM3N
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KN2QSD73XHAAAXDE9TN8FH41
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KN2QSKR8CP4WRFV16AYC5E2C
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KN2QST9XJZE642JPH6YFBFNM
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KN2QT1W2ED1V5KABVFRW4DF7
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KN2QTE7P5CKGCZSM1QJQ77M8
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KN2QTPTJV2SH0J28TPWEZ9R2
  • cancelRun - cancelling a running workflow | wrun_01KN2QTXEMEBA8JMSSWCRB8D6G
  • cancelRun via CLI - cancelling a running workflow | wrun_01KN2QV6SV22EHNMKY84A669K3
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KN2QVJJYKVXE01ZFVYHT3FC5
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KN2QW6S7GNTP2Y9MSVEK371T
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KN2QWK6JBYYVYZ34G4S47Q61
  • importMetaUrlWorkflow - import.meta.url is available in step bundles | wrun_01KN2QWSNR1Z204XZQ3HYBEB0Y
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_01KN2QWVTVE669536H42XNSC3Y

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 78 0 7
✅ example 78 0 7
✅ express 78 0 7
✅ fastify 78 0 7
✅ hono 78 0 7
✅ nextjs-turbopack 83 0 2
✅ nextjs-webpack 83 0 2
✅ nitro 78 0 7
✅ nuxt 78 0 7
✅ sveltekit 78 0 7
✅ vite 78 0 7
❌ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 71 0 14
✅ express-stable 71 0 14
✅ fastify-stable 71 0 14
✅ hono-stable 71 0 14
✅ nextjs-turbopack-canary 60 0 25
✅ nextjs-turbopack-stable 77 0 8
✅ nextjs-webpack-canary 60 0 25
✅ nextjs-webpack-stable 77 0 8
❌ nitro-stable 70 1 14
✅ nuxt-stable 71 0 14
✅ sveltekit-stable 71 0 14
✅ vite-stable 71 0 14
❌ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 71 0 14
✅ express-stable 71 0 14
✅ fastify-stable 71 0 14
✅ hono-stable 71 0 14
✅ nextjs-turbopack-canary 60 0 25
✅ nextjs-turbopack-stable 77 0 8
✅ nextjs-webpack-canary 60 0 25
✅ nextjs-webpack-stable 77 0 8
❌ nitro-stable 70 1 14
❌ nuxt-stable 70 1 14
❌ sveltekit-stable 70 1 14
✅ vite-stable 71 0 14
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 71 0 14
✅ express-stable 71 0 14
✅ fastify-stable 71 0 14
✅ hono-stable 71 0 14
✅ nextjs-turbopack-canary 60 0 25
✅ nextjs-turbopack-stable 77 0 8
✅ nextjs-webpack-canary 60 0 25
✅ nextjs-webpack-stable 77 0 8
✅ nitro-stable 71 0 14
✅ nuxt-stable 71 0 14
✅ sveltekit-stable 71 0 14
✅ vite-stable 71 0 14
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 77 0 8
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 5 0 0
❌ mongodb 56 4 8
✅ redis-dev 5 0 0
❌ redis 57 3 8
✅ turso-dev 5 0 0
❌ turso 4 56 8
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 71 0 14
✅ e2e-local-postgres-nest-stable 71 0 14
✅ e2e-local-prod-nest-stable 71 0 14

📋 View full workflow run

❌ Some E2E test jobs failed:

  • Vercel Prod: success
  • Local Dev: failure
  • Local Prod: failure
  • Local Postgres: success
  • Windows: success

Check the workflow run for details.

@VaguelySerious
[core] Combine initial run fetch, event fetch, and run_started event …
38b6674 
…creation

Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious VaguelySerious mentioned this pull request Mar 31, 2026
Open
@VaguelySerious
[core] [world] Lazy run creation on start
2f51139 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
add local and postgres world changes
0dfd424 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix get
b1c2bf3 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
changelog
9202723 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix local world
c129183 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix backend
5223192 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
e2e test
5033640 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
docs
d381cd3 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
test fixes
10838f3 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
docs
ccba633 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
fix
770c419 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
base64?
ee29ee9 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
change e2e test
11631dc 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
changeset
ddd0bfd 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
409 in case of cold start + 404 backoff when polling run values
3ed82c1 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
@VaguelySerious
remove override
7b51efd 
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
VaguelySerious
VaguelySerious commented Mar 31, 2026
View reviewed changes
packages/core/src/runtime/run.ts
// Track not-found retries separately: when run_created fails and the
// resilient start path hasn't created the run yet, runs.get throws
// WorkflowRunNotFoundError. We retry up to 3 times with back-off
// (1s, 3s, 6s = 10s total) to give the queue time to deliver.
Copy link
Copy Markdown
Member Author

@VaguelySerious VaguelySerious Mar 30, 2026

Choose a reason for hiding this comment

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

This isn't optimal. If just the initial call fails but the start ends up succeeding within seconds, it's nice that the user doesn't notice, but in other cases, when you really have the wrong run ID, your calls shouldn't be waiting for multiple seconds. What's the right UX here?

VaguelySerious
VaguelySerious commented Mar 31, 2026
View reviewed changes
docs/content/docs/changelog/resilient-start.mdx
Comment on lines +124 to +127
### Base64 encoding for queue transport

`Uint8Array` values (the serialized workflow input) don't survive JSON serialization
through the queue — they get corrupted to `{0: 72, 1: 101, ...}` objects. The `runInput`
Copy link
Copy Markdown
Member Author

@VaguelySerious VaguelySerious Mar 31, 2026

Choose a reason for hiding this comment

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

This is a hack, trying to remove this right now by devaluing binary, but might not be the right approach. WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@vercel vercel[bot] vercel[bot] left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@VaguelySerious