Skip to content

Fix CLI missing specVersion in "run_cancelled" event payload#1078

Merged
TooTallNate merged 2 commits into
mainfrom
02-15-fix_cli_missing_specversion_in_run_cancelled_event_payload
Feb 17, 2026
Merged

Fix CLI missing specVersion in "run_cancelled" event payload#1078
TooTallNate merged 2 commits into
mainfrom
02-15-fix_cli_missing_specversion_in_run_cancelled_event_payload

Conversation

@TooTallNate
Copy link
Copy Markdown
Member

The CLI's cancelRun in packages/cli/src/lib/inspect/run.ts sent { eventType: 'run_cancelled' } without specVersion, causing the Vercel API's /v2/runs/{id}/events endpoint to reject the request with a 400 error. The core runtime's cancelRun already handled this correctly, so the fix removes the redundant CLI wrapper and calls the core implementation directly.

The bug was introduced in 4966b72 ("implement event-sourced architecture (#621)") which changed the CLI cancel from world.runs.cancel(runId) to world.events.create(runId, ...) but omitted specVersion from the payload. The same commit correctly included it in Run#cancel() in core — it was simply missed in the CLI path. A later commit (86a7930) added v1Compat branching but still never added specVersion. The final merged state in a2b688d (PR #894) still omits it.

Also adds a CLI cancel e2e test that starts a long-running workflow, cancels it via the CLI command, and verifies the run status.

The CLI's `cancelRun` in `packages/cli/src/lib/inspect/run.ts` sent `{ eventType: 'run_cancelled' }` without `specVersion`, causing the Vercel API's `/v2/runs/{id}/events` endpoint to reject the request with a 400 error. The core runtime's `cancelRun` already handled this correctly, so the fix removes the redundant CLI wrapper and calls the core implementation directly.

The bug was introduced in 4966b72 ("implement event-sourced architecture (#621)") which changed the CLI cancel from `world.runs.cancel(runId)` to `world.events.create(runId, ...)` but omitted `specVersion` from the payload. The same commit correctly included it in `Run#cancel()` in core — it was simply missed in the CLI path. A later commit (86a7930) added v1Compat branching but still never added specVersion. The final merged state in a2b688d (PR #894) still omits it.

Also adds a CLI cancel e2e test that starts a long-running workflow, cancels it via the CLI command, and verifies the run status.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Feb 16, 2026

🦋 Changeset detected

Latest commit: da5e23e

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

This PR includes changesets to release 14 packages
Name Type
@workflow/cli Patch
workflow Patch
@workflow/world-testing Patch
@workflow/core Patch
@workflow/builders Patch
@workflow/next Patch
@workflow/nitro Patch
@workflow/web-shared 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 16, 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 🥇 Express 0.032s (-8.7% 🟢) 1.004s (~) 0.973s 10 1.00x
💻 Local Nitro 0.032s (+1.0%) 1.005s (~) 0.973s 10 1.01x
💻 Local Next.js (Turbopack) 0.045s 1.005s 0.960s 10 1.42x
🌐 Redis Next.js (Turbopack) 0.047s 1.004s 0.957s 10 1.49x
🌐 MongoDB Next.js (Turbopack) 0.102s 1.008s 0.905s 10 3.24x
🐘 Postgres Express 0.252s (+24.3% 🔺) 1.010s (-0.8%) 0.758s 10 7.97x
🐘 Postgres Nitro 0.487s (+114.9% 🔺) 1.010s (-0.9%) 0.523s 10 15.42x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.555s (-7.7% 🟢) 1.969s (-4.6%) 1.414s 10 1.00x
▲ Vercel Nitro 0.587s (-7.9% 🟢) 2.022s (-6.2% 🟢) 1.434s 10 1.06x
▲ Vercel Next.js (Turbopack) 0.621s (-24.4% 🟢) 1.953s (-9.6% 🟢) 1.332s 10 1.12x

🔍 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.103s 2.006s 0.903s 10 1.00x
💻 Local Express 1.105s (~) 2.005s (~) 0.900s 10 1.00x
💻 Local Nitro 1.105s (~) 2.006s (~) 0.901s 10 1.00x
🌐 Redis Next.js (Turbopack) 1.110s 2.007s 0.897s 10 1.01x
🌐 MongoDB Next.js (Turbopack) 1.309s 2.009s 0.700s 10 1.19x
🐘 Postgres Express 1.922s (-22.0% 🟢) 2.012s (-33.2% 🟢) 0.090s 10 1.74x
🐘 Postgres Nitro 2.355s (+3.7%) 3.015s (+7.2% 🔺) 0.660s 10 2.14x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.308s (+2.2%) 3.161s (-5.9% 🟢) 0.853s 10 1.00x
▲ Vercel Nitro 2.333s (+1.6%) 3.273s (-10.4% 🟢) 0.939s 10 1.01x
▲ Vercel Next.js (Turbopack) 2.571s (+6.7% 🔺) 3.281s (-6.0% 🟢) 0.710s 10 1.11x

🔍 Observability: Express | 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.725s 11.022s 0.297s 3 1.00x
💻 Local Next.js (Turbopack) 10.755s 11.022s 0.267s 3 1.00x
💻 Local Express 10.820s (-0.6%) 11.023s (~) 0.203s 3 1.01x
💻 Local Nitro 10.844s (~) 11.023s (~) 0.179s 3 1.01x
🌐 MongoDB Next.js (Turbopack) 12.320s 13.026s 0.706s 3 1.15x
🐘 Postgres Express 15.303s (-19.8% 🟢) 16.045s (-18.0% 🟢) 0.742s 2 1.43x
🐘 Postgres Nitro 20.227s (+32.7% 🔺) 21.060s (+31.3% 🔺) 0.833s 2 1.89x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 17.736s (~) 18.667s (-1.3%) 0.931s 2 1.00x
▲ Vercel Nitro 18.084s (+4.1%) 18.969s (+1.3%) 0.884s 2 1.02x
▲ Vercel Next.js (Turbopack) 18.230s (+2.5%) 19.272s (+1.4%) 1.042s 2 1.03x

🔍 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.937s 27.052s 0.114s 3 1.00x
💻 Local Next.js (Turbopack) 27.280s 28.053s 0.773s 3 1.01x
💻 Local Nitro 27.484s (~) 28.050s (~) 0.566s 3 1.02x
💻 Local Express 27.502s (-0.5%) 28.050s (~) 0.548s 3 1.02x
🌐 MongoDB Next.js (Turbopack) 30.660s 31.053s 0.393s 2 1.14x
🐘 Postgres Express 37.890s (-1.3%) 38.598s (-1.3%) 0.708s 2 1.41x
🐘 Postgres Nitro 50.541s (+33.5% 🔺) 51.135s (+34.2% 🔺) 0.595s 2 1.88x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 43.087s (-4.5%) 44.095s (-4.9%) 1.009s 2 1.00x
▲ Vercel Nitro 43.559s (+2.8%) 45.014s (+3.2%) 1.455s 2 1.01x
▲ Vercel Next.js (Turbopack) 44.250s (+2.8%) 45.619s (+3.7%) 1.369s 2 1.03x

🔍 Observability: Express | 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) 54.468s 55.098s 0.630s 2 1.00x
💻 Local Next.js (Turbopack) 56.913s 57.102s 0.190s 2 1.04x
💻 Local Nitro 57.257s (~) 58.099s (~) 0.843s 2 1.05x
💻 Local Express 57.303s (-0.7%) 58.101s (~) 0.798s 2 1.05x
🌐 MongoDB Next.js (Turbopack) 61.361s 62.094s 0.733s 2 1.13x
🐘 Postgres Express 97.480s (+29.0% 🔺) 98.239s (+29.0% 🔺) 0.759s 1 1.79x
🐘 Postgres Nitro 100.193s (+33.1% 🔺) 100.234s (+31.6% 🔺) 0.041s 1 1.84x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 89.131s (-4.6%) 90.769s (-4.3%) 1.638s 1 1.00x
▲ Vercel Nitro 89.818s (-3.1%) 90.733s (-3.0%) 0.915s 1 1.01x
▲ Vercel Next.js (Turbopack) 89.971s (-2.4%) 90.477s (-3.8%) 0.506s 1 1.01x

🔍 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.286s 2.006s 0.720s 15 1.00x
💻 Local Nitro 1.397s (~) 2.005s (~) 0.608s 15 1.09x
💻 Local Next.js (Turbopack) 1.411s 2.005s 0.594s 15 1.10x
💻 Local Express 1.419s (-0.5%) 2.004s (~) 0.586s 15 1.10x
🐘 Postgres Express 2.034s (+4.3%) 2.923s (+31.3% 🔺) 0.889s 11 1.58x
🌐 MongoDB Next.js (Turbopack) 2.169s 3.009s 0.841s 10 1.69x
🐘 Postgres Nitro 2.192s (-0.9%) 3.014s (+12.5% 🔺) 0.822s 10 1.70x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.300s (-74.6% 🟢) 3.108s (-73.2% 🟢) 0.809s 10 1.00x
▲ Vercel Nitro 2.404s (-74.4% 🟢) 3.333s (-72.7% 🟢) 0.930s 9 1.05x
▲ Vercel Next.js (Turbopack) 2.852s (-30.7% 🟢) 3.723s (-29.4% 🟢) 0.871s 9 1.24x

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

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 2.502s 3.008s 0.506s 10 1.00x
💻 Local Next.js (Turbopack) 2.572s 3.008s 0.436s 10 1.03x
💻 Local Express 2.591s (-8.2% 🟢) 3.008s (~) 0.417s 10 1.04x
💻 Local Nitro 2.619s (+1.8%) 3.007s (~) 0.388s 10 1.05x
🌐 MongoDB Next.js (Turbopack) 4.769s 5.178s 0.409s 6 1.91x
🐘 Postgres Nitro 8.641s (-13.4% 🟢) 9.042s (-12.1% 🟢) 0.401s 4 3.45x
🐘 Postgres Express 10.838s (+15.7% 🔺) 11.374s (+16.3% 🔺) 0.537s 3 4.33x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.670s (-83.9% 🟢) 3.383s (-80.9% 🟢) 0.713s 9 1.00x
▲ Vercel Express 2.835s (-84.0% 🟢) 3.596s (-81.4% 🟢) 0.761s 9 1.06x
▲ Vercel Nitro 3.163s (-78.0% 🟢) 4.201s (-73.0% 🟢) 1.038s 8 1.18x

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

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.071s 4.724s 0.653s 7 1.00x
💻 Local Nitro 7.225s (~) 8.021s (~) 0.796s 4 1.77x
💻 Local Express 7.554s (-10.3% 🟢) 8.019s (-11.1% 🟢) 0.465s 4 1.86x
💻 Local Next.js (Turbopack) 8.060s 8.518s 0.458s 4 1.98x
🌐 MongoDB Next.js (Turbopack) 9.878s 10.352s 0.473s 3 2.43x
🐘 Postgres Nitro 41.874s (-15.3% 🟢) 42.134s (-15.9% 🟢) 0.260s 1 10.29x
🐘 Postgres Express 48.778s (-4.4%) 49.155s (-3.9%) 0.377s 1 11.98x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 6.539s (-67.4% 🟢) 8.017s (-61.5% 🟢) 1.478s 4 1.00x
▲ Vercel Nitro 7.596s (-66.5% 🟢) 8.758s (-63.2% 🟢) 1.162s 4 1.16x
▲ Vercel Express 10.453s (+152.4% 🔺) 11.494s (+110.3% 🔺) 1.040s 3 1.60x

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

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 1.265s 2.006s 0.742s 15 1.00x
💻 Local Express 1.431s (-3.2%) 2.006s (~) 0.575s 15 1.13x
💻 Local Nitro 1.431s (~) 2.005s (~) 0.574s 15 1.13x
💻 Local Next.js (Turbopack) 1.480s 2.006s 0.526s 15 1.17x
🐘 Postgres Express 1.985s (-6.7% 🟢) 2.228s (-14.2% 🟢) 0.243s 14 1.57x
🐘 Postgres Nitro 2.151s (~) 2.680s (-2.2%) 0.529s 12 1.70x
🌐 MongoDB Next.js (Turbopack) 2.157s 3.009s 0.851s 10 1.71x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.264s (-4.6%) 3.279s (-2.5%) 1.015s 10 1.00x
▲ Vercel Express 2.281s (+1.9%) 3.250s (+0.9%) 0.969s 10 1.01x
▲ Vercel Next.js (Turbopack) 2.987s (+25.0% 🔺) 3.919s (+19.2% 🔺) 0.932s 8 1.32x

🔍 Observability: Nitro | Express | 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.483s 3.008s 0.524s 10 1.00x
💻 Local Nitro 2.634s (-3.0%) 3.008s (~) 0.374s 10 1.06x
💻 Local Express 2.659s (-6.2% 🟢) 3.007s (~) 0.348s 10 1.07x
💻 Local Next.js (Turbopack) 2.775s 3.009s 0.233s 10 1.12x
🌐 MongoDB Next.js (Turbopack) 4.705s 5.178s 0.473s 6 1.89x
🐘 Postgres Express 11.030s (-9.9% 🟢) 11.365s (-10.5% 🟢) 0.335s 3 4.44x
🐘 Postgres Nitro 11.764s (+17.5% 🔺) 12.036s (+12.5% 🔺) 0.272s 3 4.74x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.439s (-21.2% 🟢) 3.157s (-21.8% 🟢) 0.718s 10 1.00x
▲ Vercel Next.js (Turbopack) 2.462s (-7.4% 🟢) 3.129s (-15.5% 🟢) 0.667s 10 1.01x
▲ Vercel Nitro 2.478s (-20.1% 🟢) 3.347s (-19.0% 🟢) 0.869s 9 1.02x

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

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🌐 Redis 🥇 Next.js (Turbopack) 4.145s 4.867s 0.722s 7 1.00x
💻 Local Nitro 7.777s (+0.6%) 8.022s (-3.0%) 0.246s 4 1.88x
💻 Local Next.js (Turbopack) 7.825s 8.269s 0.444s 4 1.89x
💻 Local Express 7.831s (-9.3% 🟢) 8.267s (-8.4% 🟢) 0.436s 4 1.89x
🌐 MongoDB Next.js (Turbopack) 9.861s 10.351s 0.490s 3 2.38x
🐘 Postgres Express 50.515s (-2.1%) 51.122s (-1.9%) 0.607s 1 12.19x
🐘 Postgres Nitro 51.047s (+1.8%) 51.131s (~) 0.084s 1 12.31x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - -

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 3.599s (+12.9% 🔺) 4.519s (+11.7% 🔺) 0.919s 7 1.00x
▲ Vercel Express 3.936s (+29.5% 🔺) 4.981s (+27.5% 🔺) 1.045s 8 1.09x
▲ Vercel Nitro 5.001s (+71.6% 🔺) 6.448s (+57.6% 🔺) 1.447s 5 1.39x

🔍 Observability: Next.js (Turbopack) | Express | 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.002s 0.011s 1.017s 0.865s 10 1.00x
🌐 Redis Next.js (Turbopack) 0.153s 0.999s 0.001s 1.007s 0.854s 10 1.00x
💻 Local Nitro 0.172s (+1.8%) 1.002s (~) 0.011s (+1.8%) 1.016s (~) 0.844s 10 1.13x
💻 Local Express 0.173s (-3.9%) 1.003s (~) 0.011s (-6.8% 🟢) 1.016s (~) 0.843s 10 1.14x
🌐 MongoDB Next.js (Turbopack) 0.504s 0.947s 0.001s 1.009s 0.504s 10 3.31x
🐘 Postgres Express 1.194s (-18.3% 🟢) 1.931s (+16.6% 🔺) 0.001s (+16.7% 🔺) 2.014s (~) 0.820s 10 7.83x
🐘 Postgres Nitro 2.297s (+71.0% 🔺) 2.748s (+62.1% 🔺) 0.002s (+41.7% 🔺) 3.016s (+49.8% 🔺) 0.719s 10 15.05x
🐘 Postgres Next.js (Turbopack) ⚠️ missing - - - - -

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Next.js (Turbopack) 2.010s (-1.4%) 2.615s (~) 0.265s (+13.7% 🔺) 3.486s (+0.6%) 1.476s 10 1.00x
▲ Vercel Nitro 2.078s (-21.4% 🟢) 2.816s (-22.1% 🟢) 0.228s (+9.5% 🔺) 3.651s (-16.5% 🟢) 1.573s 10 1.03x
▲ Vercel Express 2.103s (-33.3% 🟢) 2.601s (-49.8% 🟢) 0.424s (+124.5% 🔺) 3.673s (-40.0% 🟢) 1.570s 10 1.05x

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

Summary

Fastest Framework by World

Winner determined by most benchmark wins

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

Winner determined by most benchmark wins

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

📋 View full workflow run

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 16, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 523 0 38 561
✅ 💻 Local Development 544 0 68 612
✅ 📦 Local Production 544 0 68 612
✅ 🐘 Local Postgres 544 0 68 612
✅ 🪟 Windows 48 0 3 51
❌ 🌍 Community Worlds 108 45 9 162
✅ 📋 Other 132 0 21 153
Total 2443 45 275 2763

❌ Failed Tests

🌍 Community Worlds (45 failed)

mongodb (1 failed):

  • webhookWorkflow

turso (44 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • parallelSleepWorkflow
  • 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 retry behavior workflow completes despite transient 5xx on step_completed
  • 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
  • cancelRun - cancelling a running workflow
  • 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 47 0 4
✅ example 47 0 4
✅ express 47 0 4
✅ fastify 47 0 4
✅ hono 47 0 4
✅ nextjs-turbopack 50 0 1
✅ nextjs-webpack 50 0 1
✅ nitro 47 0 4
✅ nuxt 47 0 4
✅ sveltekit 47 0 4
✅ vite 47 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 44 0 7
✅ express-stable 44 0 7
✅ fastify-stable 44 0 7
✅ hono-stable 44 0 7
✅ nextjs-turbopack-canary 48 0 3
✅ nextjs-turbopack-stable 48 0 3
✅ nextjs-webpack-canary 48 0 3
✅ nextjs-webpack-stable 48 0 3
✅ nitro-stable 44 0 7
✅ nuxt-stable 44 0 7
✅ sveltekit-stable 44 0 7
✅ vite-stable 44 0 7
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 44 0 7
✅ express-stable 44 0 7
✅ fastify-stable 44 0 7
✅ hono-stable 44 0 7
✅ nextjs-turbopack-canary 48 0 3
✅ nextjs-turbopack-stable 48 0 3
✅ nextjs-webpack-canary 48 0 3
✅ nextjs-webpack-stable 48 0 3
✅ nitro-stable 44 0 7
✅ nuxt-stable 44 0 7
✅ sveltekit-stable 44 0 7
✅ vite-stable 44 0 7
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 44 0 7
✅ express-stable 44 0 7
✅ fastify-stable 44 0 7
✅ hono-stable 44 0 7
✅ nextjs-turbopack-canary 48 0 3
✅ nextjs-turbopack-stable 48 0 3
✅ nextjs-webpack-canary 48 0 3
✅ nextjs-webpack-stable 48 0 3
✅ nitro-stable 44 0 7
✅ nuxt-stable 44 0 7
✅ sveltekit-stable 44 0 7
✅ vite-stable 44 0 7
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 48 0 3
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 47 1 3
✅ redis-dev 3 0 0
✅ redis 48 0 3
✅ turso-dev 3 0 0
❌ turso 4 44 3
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 44 0 7
✅ e2e-local-postgres-nest-stable 44 0 7
✅ e2e-local-prod-nest-stable 44 0 7

📋 View full workflow run

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Feb 16, 2026

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 Feb 16, 2026 5:17pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Feb 16, 2026 5:17pm
example-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-astro-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-express-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-fastify-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-hono-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-nitro-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-nuxt-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workbench-vite-workflow Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Feb 16, 2026 5:17pm
workflow-nest Ready Ready Preview, Comment Feb 16, 2026 5:17pm
workflow-swc-playground Ready Ready Preview, Comment Feb 16, 2026 5:17pm

@TooTallNate TooTallNate marked this pull request as ready for review February 16, 2026 07:01
Copilot AI review requested due to automatic review settings February 16, 2026 07:01
Copy link
Copy Markdown
Member Author

TooTallNate commented Feb 16, 2026

@TooTallNate TooTallNate requested review from a team and removed request for Copilot February 16, 2026 07:01
Copilot AI review requested due to automatic review settings February 16, 2026 07:37
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 fixes a bug where the CLI's cancelRun function was missing the specVersion field in the "run_cancelled" event payload, causing the Vercel API to reject requests with a 400 error. The fix removes the buggy CLI-specific implementation and uses the core runtime's cancelRun function directly, which correctly includes specVersion. The PR also adds e2e test coverage for canceling a running workflow.

Changes:

  • Removed buggy cancelRun implementation from CLI that omitted specVersion
  • Updated cancel command to import cancelRun from core runtime instead
  • Added e2e test that cancels a running workflow and verifies the cancellation

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
packages/cli/src/lib/inspect/run.ts Removed buggy cancelRun function that was missing specVersion in event payload
packages/cli/src/commands/cancel.ts Changed import to use core runtime's cancelRun instead of CLI wrapper
packages/core/e2e/utils.ts Added cliCancel utility function for CLI-based cancel testing
packages/core/e2e/e2e.test.ts Added test that cancels a running workflow and verifies status
.changeset/purple-paths-pump.md Added changeset entry for the CLI fix

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

Comment thread packages/core/e2e/utils.ts Outdated
@TooTallNate TooTallNate force-pushed the 02-15-fix_cli_missing_specversion_in_run_cancelled_event_payload branch from 404cee5 to da5e23e Compare February 16, 2026 17:14
@TooTallNate TooTallNate merged commit 262ef3a into main Feb 17, 2026
105 checks passed
@TooTallNate TooTallNate deleted the 02-15-fix_cli_missing_specversion_in_run_cancelled_event_payload branch February 17, 2026 02:16
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