[world-vercel] Fix deploymentId "latest" resolving against the wrong team by VaguelySerious · Pull Request #3844 · vercel/workflow

VaguelySerious · 2026-08-27T15:51:01Z

Problem

Resolving deploymentId: "latest" is the only start() path that calls api.vercel.com, and that endpoint reads the source deployment out of a team-partitioned store. The identity the request presents therefore decides which team's deployments are visible, which makes the credential choice a correctness concern rather than an auth detail.

Two things combined to send the request to the wrong team:

resolveVercelApiToken prefers process.env.VERCEL_TOKEN over the OIDC token. A VERCEL_TOKEN set in a deployed function's environment for unrelated tooling silently displaced the deployment's own identity.
The request carried no team scoping at all: no teamId query parameter, and no x-vercel-team-id (that header is only read by the proxy endpoint, never by the API's team auth).

A VERCEL_TOKEN is a user credential and carries no team, so with no team specified the API scopes the lookup to the token owner's default team. When that is not the team owning the deployment, the partitioned lookup misses and returns 404 Deployment not found for a deployment that is READY and plainly visible in the dashboard.

This is why only "latest" broke while every other workflow operation kept working: everything else talks to the workflow backend with the OIDC token, and pinning a deployment ID skips this call entirely.

Evidence

Traces for the affected project, over 22 requests, were unanimous:

workflow.auth.token_type: "token" (never vercel-oidc)
workflow.team_id set to a team that owns none of the project's deployments
workflow.failure.reason: source_deployment_not_found

The split by auth type over 7 days shows the resolver itself is healthy and the failures track the credential:

token type	calls	`source_deployment_not_found`
`vercel-oidc`	519,330	0
`token`	31,796	23
`app-token`	19	1

Fix

Prefer the OIDC token inside the Vercel runtime. Its owner_id claim names exactly the team that owns the deployment. An explicit config.token still wins, and outside the runtime (CLI, CI, dashboard) the original order is kept, where VERCEL_TOKEN is usually set deliberately and there is no deployment identity to prefer. If OIDC is unavailable in the runtime, it still falls back to VERCEL_TOKEN.
Send ?teamId= from projectConfig.teamId, the same way the sibling run-key request already does. This fixes the CLI/dashboard path for anyone whose default team differs from the project's.
Name identity as the cause in the 404 message. It previously read as a missing deployment, which sends readers to inspect deployment state instead of the credential.

Testing

Six tests added to resolve-latest-deployment.test.ts covering OIDC-over-VERCEL_TOKEN in the runtime, the unchanged order outside it, explicit config token precedence, the OIDC-unavailable fallback, the teamId parameter and its absence, and the 404 message.

The existing suite could not have caught this: its OIDC test explicitly deletes VERCEL_TOKEN, so the both-present case (which is what production looks like) was untested, and the neighbouring test called VERCEL_TOKEN a "fall back" when it was in fact the winner.

Separately verified against a stub of the API handler's team-resolution logic that the reported scenario now resolves both in-deployment and from the CLI with teamId configured, and still reports a clear error when neither identity nor team is available. That simulation was validation-only and is not included here.

Notes for reviewers

The docs note is added to both v4 and v5 start.mdx, since both describe deploymentId: "latest".
Worth considering as a follow-up on the API side: for a deployment-scoped lookup, falling back to the caller's defaultTeamId yields a confusing 404 rather than a clear "no team specified". Out of scope here.

Docs Preview

Page	v5	v4
`start()` — `deploymentId: "latest"`	/docs/api-reference/workflow-api/start	/v4/docs/api-reference/workflow-api/start

These require Vercel team access (deployment protection).

🤖 Generated with Claude Code

…team Resolving `deploymentId: "latest"` is the only `start()` path that calls api.vercel.com, and that endpoint reads the source deployment out of a team-partitioned store. The identity the request presents therefore decides which team's deployments are visible. `resolveVercelApiToken` prefers `process.env.VERCEL_TOKEN` over the OIDC token, so a `VERCEL_TOKEN` present in a deployed function's environment for unrelated tooling displaced the deployment's own identity. A `VERCEL_TOKEN` is a user credential and carries no team, and the request sent no team scoping either, so the API fell back to the token owner's default team. When that was not the team owning the deployment, the lookup missed its partition and returned 404 "Deployment not found" for a deployment that was READY and plainly visible in the dashboard. Inside the Vercel runtime the OIDC token now wins, since its `owner_id` claim names exactly the right team. Outside the runtime the original order is kept, and the request now carries `?teamId=` from `projectConfig.teamId` the same way the sibling run-key request already does. The 404 message also names identity as the cause. It previously read as a missing deployment, which sends readers to inspect deployment state instead of the credential. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

changeset-bot · 2026-08-27T15:51:05Z

🦋 Changeset detected

Latest commit: e8a79d5

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

This PR includes changesets to release 17 packages

Name	Type
@workflow/world-vercel	Patch
@workflow/cli	Patch
@workflow/core	Patch
@workflow/web	Patch
workflow	Patch
@workflow/world-testing	Patch
@workflow/builders	Patch
@workflow/next	Patch
@workflow/nitro	Patch
@workflow/vitest	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

vercel · 2026-08-27T15:51:08Z

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

Project	Deployment	Actions	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview, v0	Aug 27, 2026 3:55pm
example-nextjs-workflow-webpack	Ready	Preview, v0	Aug 27, 2026 3:55pm
example-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-astro-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-express-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-fastify-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-hono-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-nestjs-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-nitro-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-nuxt-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-python-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-sveltekit-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-tanstack-start-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workbench-vite-workflow	Ready	Preview, v0	Aug 27, 2026 3:55pm
workflow-docs	Ready	Preview, v0	Aug 27, 2026 3:55pm
workflow-swc-playground	Ready	Preview, v0	Aug 27, 2026 3:55pm
workflow-tarballs	Ready	Preview, v0	Aug 27, 2026 3:55pm
workflow-web	Ready	Preview, v0	Aug 27, 2026 3:55pm

github-actions · 2026-08-27T15:51:21Z

📊 Workflow Benchmarks

commit e8a79d5 · Thu, 27 Aug 2026 16:16:22 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric	Scenario	Best (ms)	P75 (ms)	P90 (ms)	P99 (ms)	Samples
TTFS	step	200 (-6.5%)	1310 🔴 (+19%) 🔻	1335 🔴 (+17%) 🔻	1390 🔴 (+18%) 🔻	30
TTFS	stream	190 (-4.5%)	1319 🔴 (+20%) 🔻	1350 🔴 (+16%) 🔻	1392 🔴 (-3.9%)	30
TTFS	hook + stream	1151 (+7.9%)	1705 🔴 (+24%) 🔻	1773 🔴 (+26%) 🔻	6131 🔴 (+253%) 🔻	30
Fan-out TTFS	Promise.all(100 steps)	515 (-20%) 💚	1925 (+8.8%)	1938 (+6.4%)	2346 (+27%) 🔻	10
Fan-out TTLS	Promise.all(100 steps)	1928 (-6.4%)	3711 (-7.3%)	4405 (+6.6%)	4421 (+0.9%)	10
STSO	1020 steps (inline)	123 (+24%) 🔻	158 (-4.8%)	176 (-13%)	281 (-19%) 💚	1019
WO	1020 steps	156009 (-2.9%)	156009 (-2.9%)	156009 (-2.9%)	156009 (-2.9%)	1
CRTT	first chunk (pooled)	100 (-2.0%)	175 (+5.4%)	210 (+4.0%)	322 (-90%) 💚	28

Streams

Scenario	CRTT 1st	p75	p90	p99	CDV max	iters
paced control (100/s, 60B)	135 (-9%)	174 (-16%)	328 (+10%)	515 (-1%)	151 (-15%)	10
size sweep (100/s, 160B-12KB)	120 (-15%)	166 (-35%)	222 (-44%)	518 (-61%)	165 (-38%)	10
replay gateway-gpt-5.4-nano-2000t (1x)	153 (-3%)	141 (-45%)	192 (-86%)	371 (-88%)	292 (-16%)	3
replay eve-gpt-5.6-sol-2000t (1x)	123 (-10%)	146 (-23%)	191 (-27%)	314 (-29%)	313 (-32%)	2
replay eve-gpt-5.6-sol-2000t (2x)	175 (+5%)	217 (-99%)	318 (-99%)	1410 (-95%)	290 (-56%)	3

📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 160359ms → this run 155861ms (Δ -4498ms, -3%)

 50-100 ms ┃ main 1 this 0 -1
100-150 ms ███████████████████████┃ main 591 this 613 +22
150-200 ms ████████████░┃ main 314 this 368 +54
200-250 ms ┃██ main 78 this 21 -57
250-300 ms ┃ main 19 this 9 -10
300-350 ms ┃ main 7 this 1 -6
350-400 ms ┃ main 3 this 2 -1
400-450 ms ┃ main 2 this 4 +2
450-500 ms ┃ main 2 this 0 -2
500-550 ms ┃ main 1 this 1 +0
550-600 ms ┃ main 1 this 0 -1

📈 CRTT drill-down vs main (RTT distributions & profiles)

variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▂▁··· 148.5 (-9%) 129 (-10%) 328 (+10%) 515 (-1%) 3000
sweep ······▂█▂▁··· 140.4 (-32%) 130 (-19%) 222 (-44%) 518 (-61%) 3000
gw 1x ·····▁▄█▁···· 123.1 (-50%) 114 (-19%) 192 (-86%) 371 (-88%) 5295
eve 1x ·····▁▅█▂···· 122.8 (-22%) 110 (-16%) 191 (-27%) 314 (-29%) 5186
eve 2x ·····▁▂█▃▁▁·· 185.7 (-93%) 153 (-16%) 318 (-99%) 1410 (-95%) 7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):

control ▅▄█▂▂▅▄▅▆▁ 123–181ms
sweep ▆▆▅▂▂▁▄▆▁█ 125–160ms
gw 1x ▆▄▆█▂▆▂▃▄▁ 107–142ms
eve 1x ▂▁▁▂▁▆██▄▂ 109–150ms
eve 2x ▃▁▃▄█▁▄█▃▂ 133–272ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):

sweep █▅▂▃▃▁█ 139–142ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):

control ▄▆▅▁▃█▄█▂▃ 34–56ms
sweep ▃▅▁▅▄▃█▃▄▃ 41–67ms
gw 1x ▄▄█▄▃█▄▄▂▁ 32–41ms
eve 1x ▁▄▁▂▇▅█▆█▆ 20–28ms
eve 2x ▅▄▂█▃▁▅▄▁▃ 22–33ms

ℹ️ Metric definitions & methodology

_{Streams: first-chunk RTT (the stream-open path, before any buffering/backpressure), CRTT percentiles, and worst delivery stall (CDV max). Cells are medians across iterations; per-run values in the artifacts. No 🔴/🟢 marks until targets attach.}

_{The collapsed STSO distribution section above buckets every step gap, split inline (same warm process — pure framework overhead) vs queue-hop (fresh process — dispatch, reinit, replay). █ = main, ┃ = this run, ░ = fill.}

_{The collapsed CRTT drill-down: per-variant RTT histograms (fixed log bins, · = empty) and mean RTT/positive-CDV profile lines over stream progress and chunk size. Histograms, avgs, and profiles merge exactly across runs; p50–p99 are percentile-of-percentiles. Per-index rows live in the artifacts.}

_{Best/P75/P90/P99 deltas compare against the most recent benchmark run on main at the time of this run. 🔻 flags a delta worse than +15%, 💚 one better than −15%.}

_{Metrics — TTFS: time to first step body (in-deployment start() → first step body) · Fan-out TTFS: fan-out time to first step (in-deployment start() → first of the parallel step bodies to complete) · Fan-out TTLS: fan-out time to last step (in-deployment start() → last of the parallel step bodies to complete, i.e. when the Promise.all resolves) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · CRTT: chunk round-trip time (per-chunk write → read latency, one clock domain: deployment → stream backend → same deployment) · CDV: chunk delay variation / delivery jitter (inter-arrival gap minus inter-write gap per seq-adjacent pair; skew-free; the row is each run's MAX positive value, so one stall moves it)}

_{Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · Promise.all(100 steps): 100 trivial no-op steps started together in a single Promise.all; Fan-out TTFS is the first of them to complete and Fan-out TTLS the last, both from the in-deployment clientStart, so their gap is the spread the runtime adds across the fan-out · paced control (100/s, 60B): the control: 300 tiny (~60B) deltas metronome-paced at 100/s — zero workload structure, so it reads the transport floor and flush cadence, and disambiguates transport-wide vs workload-specific when a replay row moves · size sweep (100/s, 160B-12KB): same pacing as the control with deltas padded in rotation across seven log-spaced sizes (~160B–12KB) — rotation decouples size from stream position, so it isolates whether chunk size causes latency · replay gateway-gpt-5.4-nano-2000t (1x): raw provider SSE cadence captured at the AI gateway boundary (gpt-5.4-nano, the most popular gateway model; per-token deltas p50 208B = the modal production chunk size), replayed exactly as measured — the typical customer's workload; its CDV is the typical customer's real delivery jitter · replay eve-gpt-5.6-sol-2000t (1x): a captured eve turn (gpt-5.6-sol, the most-used demanding eve model; ~2000 output tokens = production p50 turn length) replayed exactly as measured — eve's envelope protocol re-ships the cumulative message so sizes ramp 142B→13KB; the demanding outlier tenant's reality · replay eve-gpt-5.6-sol-2000t (2x): the same eve capture at 2x — the headroom/stress row; real fast-tier models emit the same chunk sizes at proportionally higher rate, so time compression is a faithful speed model · first chunk (pooled): every run's seq-0 RTT pooled across all stream scenarios — the first chunk precedes any workload differentiation, so pooling samples one shared stream-open path with exact percentiles}

_{Replay cadences (semantic sha256) — eve-gpt-5.6-sol-2000teaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041}

_{🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600}

_{All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = start() → first step body (includes dispatch + any cold start); Fan-out TTFS/TTLS = first/last step completion of one Promise.all from the same anchor (the gap is the runtime’s fan-out spread); STSO/WO between step bodies; CRTT inside the workflow (excludes the api.vercel.com read path).}

_{Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor.}

github-actions · 2026-08-27T15:51:23Z

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

▲ Vercel Production (8 failed)

python-node (8 failed):

promiseAllWorkflow | wrun_41M11YW3BR0GRYRDT48EDN90M2 | 🔍 observability
sleepingWorkflow | wrun_41M11YWRW40GG7HG0XAGBWTRRY | 🔍 observability
parallelSleepWorkflow | wrun_41M11YWS4K0GX648EMVKVPZW1N | 🔍 observability
nullByteWorkflow | wrun_41M11YWZKR0GX1CTVBA0ACBZP1 | 🔍 observability
cancelRun - cancelling a running workflow | wrun_41M11Z1BD80GQP6J99AYGCNJJ2 | 🔍 observability
cancelRun via CLI - cancelling a running workflow | wrun_41M11Z1C5E0GV7T3G3FAZ340ZG | 🔍 observability
sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M11Z1N0B0GTH88VBVHPMH1DG | 🔍 observability
resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M11Z26YJ0GQ79ZKX350TA9P9 | 🔍 observability

🌐 Cross-language Conformance (9 failed)

python (9 failed):

deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M11Z42Y3KW9NNG6AGH8KMKHT
promiseAllWorkflow | wrun_41M11YW3BR0GRYRDT48EDN90M2
sleepingWorkflow | wrun_41M11YWRW40GG7HG0XAGBWTRRY
parallelSleepWorkflow | wrun_41M11YWS4K0GX648EMVKVPZW1N
nullByteWorkflow | wrun_41M11YWZKR0GX1CTVBA0ACBZP1
cancelRun - cancelling a running workflow | wrun_41M11Z1BD80GQP6J99AYGCNJJ2
cancelRun via CLI - cancelling a running workflow | wrun_41M11Z1C5E0GV7T3G3FAZ340ZG
sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M11Z1N0B0GTH88VBVHPMH1DG
resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M11Z26YJ0GQ79ZKX350TA9P9

⚠️ Flaky E2E Tests (passed on retry)

These tests failed at least once and passed on a retry. A recurring entry here is a real race worth investigating.

cancelRun via CLI - cancelling a running workflow (express)
hookCleanupTestWorkflow - hook token reuse after workflow completion (nextjs-turbopack)
hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep (nextjs-webpack)
hookWorkflow (tanstack-start)

🛠 Infra Events (absorbed by the harness)

Platform anomalies the e2e harness detected and worked around (e.g. a run the queue never picked up, replaced by a fresh run). Clustered timestamps indicate a backend blip; a steady drip indicates a platform issue worth escalating.

32 infra events

cold-start-warmup · suite warmup (python) · at 15:54:27Z · abandoned wrun_41M11YRC9M0GV3TPNT2R23V8WM · (+7 more)
run-pickup-stall · promiseAllWorkflow (python) · at 15:54:43Z · abandoned wrun_41M11YW1AK0GKWS2ABG75FX71J
run-pickup-stall · nullByteWorkflow (python) · at 15:54:43Z · abandoned wrun_41M11YW1AT0GVKZG9VEYX5CCQ2
run-pickup-stall · sleepingWorkflow (python) · at 15:54:44Z · abandoned wrun_41M11YW1AQ0GQXCKPXJS2PEGQ7
run-pickup-stall · parallelSleepWorkflow (python) · at 15:54:44Z · abandoned wrun_41M11YW1AQ0GQXCKPXJS2PEGQ8
run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 15:54:44Z · abandoned wrun_41M11YW1QZ0GKT4AG0S8CTZGZT
run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 15:55:17Z · abandoned wrun_41M11YX2840GM0GE6JM4HW7XQH
run-pickup-stall · promiseAllWorkflow (python) · at 15:55:44Z · abandoned wrun_41M11YXWRP0GN8TFFVF35M4DJG
run-pickup-stall · sleepingWorkflow (python) · at 15:55:44Z · abandoned wrun_41M11YXWYM0GV6SNP96TCEKGSF
run-pickup-stall · nullByteWorkflow (python) · at 15:55:44Z · abandoned wrun_41M11YXWX10GQFS5WB8CVBR078
run-pickup-stall · parallelSleepWorkflow (python) · at 15:55:45Z · abandoned wrun_41M11YXWX50GGXJNCZ2KKHN61P
run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 15:56:35Z · abandoned wrun_41M11YY23M0GWAKHJ6WGVY5PFP
cold-start-warmup · suite warmup (tanstack-start) · at 15:56:37Z · abandoned wrun_01M11YZ5NYZWZ4PZ178HC7XS43
cold-start-warmup · suite warmup (python) · at 15:57:36Z · abandoned wrun_01M11YY4GJZ7SSCCHGYB6QWMQK · (+7 more)
run-pickup-stall · promiseAllWorkflow (python) · at 15:57:51Z · abandoned wrun_01M11Z1SN0C69C3X98YG3EQQJ5
run-pickup-stall · parallelSleepWorkflow (python) · at 15:57:51Z · abandoned wrun_01M11Z1SN66B9YVJD7VJ290STH
run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 15:57:51Z · abandoned wrun_01M11Z1SMZ6N6K5PTD6YAAJCTF
run-pickup-stall · sleepingWorkflow (python) · at 15:57:51Z · abandoned wrun_01M11Z1SN5A80WP51N091F0YGS
run-pickup-stall · nullByteWorkflow (python) · at 15:57:51Z · abandoned wrun_01M11Z1SN9JBMVFD0RT8TCGNME
run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 15:58:16Z · abandoned wrun_41M11Z0MN80GQR9AJ1N0PNQAD2
run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 15:58:51Z · abandoned wrun_01M11Z3M8S8V1BEQMC134HPD4G
run-pickup-stall · promiseAllWorkflow (python) · at 15:58:51Z · abandoned wrun_01M11Z3M8V6DWAAB9G1Z0FRKSP
run-pickup-stall · parallelSleepWorkflow (python) · at 15:58:51Z · abandoned wrun_01M11Z3M8ZD3BX947NG3X5N1FQ
run-pickup-stall · sleepingWorkflow (python) · at 15:58:51Z · abandoned wrun_01M11Z3M8W4XCQ8JWN66V7JSJZ
run-pickup-stall · nullByteWorkflow (python) · at 15:58:51Z · abandoned wrun_01M11Z3M92DQ4CXMZN3VYTNXCY
run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 15:58:56Z · abandoned wrun_41M11Z0T050GSG93J47SEEHYWB
run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 15:59:51Z · abandoned wrun_01M11Z5EWEK96JMTST4283BCC3
run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 15:59:51Z · abandoned wrun_01M11Z5EWCSH76F5G057DDRYGE
run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 15:59:51Z · abandoned wrun_01M11Z5EWK7875XSM9C10W7TV8
run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 16:00:21Z · abandoned wrun_01M11Z6C7XPTYAG4CZD8TJCVQX
run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 16:00:21Z · abandoned wrun_01M11Z6C8100HE2YB886CRDXQX
run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 16:00:51Z · abandoned wrun_01M11Z79FPRE7S1ED7NSFF6NB8

E2E Test Summary

Summary

	Passed	Failed	Skipped	Total
❌ ▲ Vercel Production	3570	8	742	4320
✅ 💻 Local Development	3922	0	558	4480
✅ 📦 Local Production	3922	0	558	4480
✅ 🐘 Local Postgres	3922	0	558	4480
✅ 🪟 Windows	320	0	0	320
❌ 🌐 Cross-language Conformance	0	9	132	141
✅ vercel-http-transport	817	0	143	960
✅ vercel-multi-region	27	0	0	27
✅ vercel-ws-transport	553	0	87	640
Total	17053	17	2778	19848

Details by Category

❌ ▲ Vercel Production

App	Passed	Failed	Skipped
✅ astro-node	132	0	28
✅ astro-quickjs	132	0	28
✅ example-node	132	0	28
✅ example-quickjs	132	0	28
✅ express-node	132	0	28
✅ express-quickjs	132	0	28
✅ fastify-node	132	0	28
✅ fastify-quickjs	132	0	28
✅ hono-node	132	0	28
✅ hono-quickjs	132	0	28
✅ nest-node	132	0	28
✅ nest-quickjs	132	0	28
✅ nextjs-turbopack-node	157	0	3
✅ nextjs-turbopack-quickjs	157	0	3
✅ nextjs-webpack-node	157	0	3
✅ nextjs-webpack-quickjs	157	0	3
✅ nitro-node	132	0	28
✅ nitro-quickjs	132	0	28
✅ nuxt-node	132	0	28
✅ nuxt-quickjs	132	0	28
❌ python-node	0	8	152
✅ sveltekit-node	151	0	9
✅ sveltekit-quickjs	151	0	9
✅ tanstack-start-node	132	0	28
✅ tanstack-start-quickjs	132	0	28
✅ vite-node	132	0	28
✅ vite-quickjs	132	0	28

✅ 💻 Local Development

App	Passed	Skipped
✅ astro-stable-node	134	26
✅ astro-stable-quickjs	134	26
✅ express-stable-node	134	26
✅ express-stable-quickjs	134	26
✅ fastify-stable-node	134	26
✅ fastify-stable-quickjs	134	26
✅ hono-stable-node	134	26
✅ hono-stable-quickjs	134	26
✅ nest-stable-node	134	26
✅ nest-stable-quickjs	134	26
✅ nextjs-turbopack-canary-node	141	19
✅ nextjs-turbopack-canary-quickjs	141	19
✅ nextjs-turbopack-stable-node	160	0
✅ nextjs-turbopack-stable-quickjs	160	0
✅ nextjs-webpack-canary-node	141	19
✅ nextjs-webpack-canary-quickjs	141	19
✅ nextjs-webpack-stable-node	160	0
✅ nextjs-webpack-stable-quickjs	160	0
✅ nitro-stable-node	134	26
✅ nitro-stable-quickjs	134	26
✅ nuxt-stable-node	134	26
✅ nuxt-stable-quickjs	134	26
✅ sveltekit-stable-node	153	7
✅ sveltekit-stable-quickjs	153	7
✅ tanstack-start-node	134	26
✅ tanstack-start-quickjs	134	26
✅ vite-stable-node	134	26
✅ vite-stable-quickjs	134	26

✅ 📦 Local Production

App	Passed	Skipped
✅ astro-stable-node	134	26
✅ astro-stable-quickjs	134	26
✅ express-stable-node	134	26
✅ express-stable-quickjs	134	26
✅ fastify-stable-node	134	26
✅ fastify-stable-quickjs	134	26
✅ hono-stable-node	134	26
✅ hono-stable-quickjs	134	26
✅ nest-stable-node	134	26
✅ nest-stable-quickjs	134	26
✅ nextjs-turbopack-canary-node	141	19
✅ nextjs-turbopack-canary-quickjs	141	19
✅ nextjs-turbopack-stable-node	160	0
✅ nextjs-turbopack-stable-quickjs	160	0
✅ nextjs-webpack-canary-node	141	19
✅ nextjs-webpack-canary-quickjs	141	19
✅ nextjs-webpack-stable-node	160	0
✅ nextjs-webpack-stable-quickjs	160	0
✅ nitro-stable-node	134	26
✅ nitro-stable-quickjs	134	26
✅ nuxt-stable-node	134	26
✅ nuxt-stable-quickjs	134	26
✅ sveltekit-stable-node	153	7
✅ sveltekit-stable-quickjs	153	7
✅ tanstack-start-node	134	26
✅ tanstack-start-quickjs	134	26
✅ vite-stable-node	134	26
✅ vite-stable-quickjs	134	26

✅ 🐘 Local Postgres

App	Passed	Skipped
✅ astro-stable-node	134	26
✅ astro-stable-quickjs	134	26
✅ express-stable-node	134	26
✅ express-stable-quickjs	134	26
✅ fastify-stable-node	134	26
✅ fastify-stable-quickjs	134	26
✅ hono-stable-node	134	26
✅ hono-stable-quickjs	134	26
✅ nest-stable-node	134	26
✅ nest-stable-quickjs	134	26
✅ nextjs-turbopack-canary-node	141	19
✅ nextjs-turbopack-canary-quickjs	141	19
✅ nextjs-turbopack-stable-node	160	0
✅ nextjs-turbopack-stable-quickjs	160	0
✅ nextjs-webpack-canary-node	141	19
✅ nextjs-webpack-canary-quickjs	141	19
✅ nextjs-webpack-stable-node	160	0
✅ nextjs-webpack-stable-quickjs	160	0
✅ nitro-stable-node	134	26
✅ nitro-stable-quickjs	134	26
✅ nuxt-stable-node	134	26
✅ nuxt-stable-quickjs	134	26
✅ sveltekit-stable-node	153	7
✅ sveltekit-stable-quickjs	153	7
✅ tanstack-start-node	134	26
✅ tanstack-start-quickjs	134	26
✅ vite-stable-node	134	26
✅ vite-stable-quickjs	134	26

✅ 🪟 Windows

App	Passed	Failed	Skipped
✅ nextjs-turbopack-node	160	0	0
✅ nextjs-turbopack-quickjs	160	0	0

❌ 🌐 Cross-language Conformance

App	Passed	Failed	Skipped
❌ python	0	9	132

✅ vercel-http-transport

App	Passed	Skipped
✅ example	132	28
✅ express	132	28
✅ hono	132	28
✅ nextjs-turbopack	157	3
✅ nitro	132	28
✅ vite	132	28

✅ vercel-multi-region

App	Passed	Failed	Skipped
✅ nextjs-turbopack	27	0	0

✅ vercel-ws-transport

App	Passed	Skipped
✅ example	132	28
✅ express	132	28
✅ nextjs-turbopack	157	3
✅ vite	132	28

📋 View full workflow run

github-actions · 2026-08-27T15:54:43Z

Sim World

Simulated world deterministic testing for races. Traces

🟠 world-sim scenario book — 1 fail of 41 total

fence=per-spec

scenario	outcome	events	virt	replay
✅ `smoke-no-steps`	completed	3	0ms	ok
✅ `smoke-one-step`	completed	6	0ms	ok
✅ `hook-at-step-started`	completed	12	0ms	ok
✅ `hook-at-step-completed`	completed	12	0ms	ok
✅ `hook-at-hook-created`	completed	12	0ms	ok
✅ `deadline-hook-wins`	completed	7	1.0h	ok
✅ `deadline-expires`	completed	7	1.0h	ok
✅ `long-sleep`	completed	11	30.0d	ok
✅ `hook-never-arrives`	stalled	3	0ms	skipped
✅ `step-retries-twice`	completed	10	2.0s	ok
✅ `parallel-steps`	completed	9	0ms	ok
✅ `hook-on-execution-state`	completed	12	0ms	ok
✅ `peek-hook-before-branch`	completed	12	0ms	ok
✅ `peek-hook-after-branch`	completed	12	0ms	ok
✅ `peek-hook-at-registration`	completed	12	0ms	ok
✅ `race-hook-before-probe`	completed	12	0ms	ok
✅ `race-hook-after-probe`	completed	12	0ms	ok
✅ `race-duplicate-delivery`	completed	13	0ms	ok
✅ `attr-hook-before-step`	completed	11	0ms	ok
✅ `attr-hook-after-step`	completed	11	0ms	ok
✅ `attr-from-step-body`	completed	13	0ms	ok
✅ `fork-hook-after-timeout`	completed	14	1.0m	ok
✅ `fork-hook-before-timeout`	completed	14	1.0m	ok
✅ `count-hook-after-timeout`	completed	17	1.0m	ok
✅ `count-hook-before-timeout`	completed	20	1.0m	ok
✅ `stale-read-step-count-fork`	completed	20	1.0m	ok
✅ `stale-read-equal-step-counts`	completed	14	1.0m	ok
✅ `step-vs-step-fork`	completed	12	0ms	ok
✅ `step-vs-step-fork-fenced`	completed	12	0ms	ok
✅ `fence-catches-benign-direction`	completed	12	5ms	ok
✅ `in-flight-before-decision`	completed	17	1.0m	ok
❌ `in-flight-before-decision-counted`	completed	17	1.0m	ok
✅ `in-flight-after-decision`	completed	19	2.0m	ok
✅ `stale-read-step-count-fork-fenced`	completed	20	1.0m	ok
✅ `fork-hook-wins`	completed	13	1.0m	ok
✅ `fork-timeout-wins`	completed	13	1.0m	ok
✅ `unclaimed-payload-under-fork`	completed	17	1.0m	ok
✅ `claimed-payload-under-fork`	completed	17	1.0m	ok
✅ `writers-independent-step-bodies`	completed	12	0ms	ok
✅ `writers-scripted-tempo`	completed	12	0ms	ok
✅ `cancel-mid-step`	cancelled	7	0ms	skipped

Full trace: world-sim.txt

github-actions · 2026-08-27T15:55:38Z

Framework	Flow route	Step reg.	Framework output
hono	200.9 KiB (±0)	40.3 KiB (±0)	1.76 MiB (+636 B)
nextjs-turbopack	206.3 KiB (±0)	439 B (±0)	763.3 KiB (+182 B)

About these numbers

Sizes are gzip; parentheses show the change against main.
Flow route and Step reg. gate this job, on raw bytes rather than the gzip shown, at max(2%, 50.0 KiB). Framework output is informational.

e8a79d5 · run

Copilot

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

github-actions · 2026-08-27T16:52:41Z

Backport PR opened against stable: #3848. Merge conflicts were resolved by AI — please review carefully. (backport job run)

…team (#3844) (#3848) Signed-off-by: Peter Wielander <mittgfu@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

vercelBotdeployed to Preview – workbench-python-workflow August 27, 2026 15:51 View deployment

vercelBotdeployed to Preview – workflow-web August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-astro-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workflow-tarballs August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-sveltekit-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – example-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-nestjs-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-nitro-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-express-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-fastify-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-hono-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-nuxt-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-vite-workflow August 27, 2026 15:52 View deployment

vercelBotdeployed to Preview – workbench-tanstack-start-workflow August 27, 2026 15:53 View deployment

vercelBotdeployed to Preview – example-nextjs-workflow-turbopack August 27, 2026 15:53 View deployment

vercelBotdeployed to Preview – example-nextjs-workflow-webpack August 27, 2026 15:53 View deployment

vercelBotdeployed to Preview – workflow-docs August 27, 2026 15:53 View deployment

vercelBotdeployed to Preview – workflow-swc-playground August 27, 2026 15:55 View deployment

TooTallNate marked this pull request as ready for review August 27, 2026 16:40

TooTallNate requested review from a team, fantix and msullivan as code owners August 27, 2026 16:40

CopilotAI lite review requested due to automatic review settings August 27, 2026 16:40

CopilotAI reviewed Aug 27, 2026

TooTallNate approved these changes Aug 27, 2026
View reviewed changes

VaguelySerious merged commit cc6eb7e into mainAug 27, 2026
318 of 324 checks passed

VaguelySerious deleted the peter/resolve-latest-deployment-team-scope branch August 27, 2026 16:48

github-actionsBot mentioned this pull request Aug 27, 2026
Version Packages (beta) #3826
Open

This was referenced Aug 27, 2026
Backport #3844: [world-vercel] Fix deploymentId "latest" resolving against the wrong team #3848
Merged
Version Packages (beta) ben-vargas/workflow#104
Open
Version Packages (beta) Jokacar10/jkworkflow#519
Open

This was referenced Aug 27, 2026
Version Packages #3834
Open
Version Packages (beta) Thegreatsura/workflow#1
Open
Version Packages (beta) erickirt/workflow#523
Open

Navigation Menu

Uh oh!

[world-vercel] Fix deploymentId "latest" resolving against the wrong team - #3844

[world-vercel] Fix deploymentId "latest" resolving against the wrong team#3844
VaguelySerious merged 1 commit into
mainfrom
peter/resolve-latest-deployment-team-scope

VaguelySerious commented Aug 27, 2026•
edited
Loading

Uh oh!

changeset-botBot commented Aug 27, 2026

Uh oh!

vercelBot commented Aug 27, 2026•
edited
Loading

Uh oh!

github-actionsBot commented Aug 27, 2026•
edited
Loading

Uh oh!

github-actionsBot commented Aug 27, 2026•
edited
Loading

Uh oh!

github-actionsBot commented Aug 27, 2026

Uh oh!

github-actionsBot commented Aug 27, 2026

Uh oh!

CopilotAI left a comment

Uh oh!

Uh oh!

github-actionsBot commented Aug 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

VaguelySerious commented Aug 27, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Evidence

Fix

Testing

Notes for reviewers

Docs Preview

Uh oh!

changeset-botBot commented Aug 27, 2026

🦋 Changeset detected

Uh oh!

vercelBot commented Aug 27, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actionsBot commented Aug 27, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📊 Workflow Benchmarks

Uh oh!

github-actionsBot commented Aug 27, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 E2E Test Results

❌ Failed E2E Tests

▲ Vercel Production (8 failed)

🌐 Cross-language Conformance (9 failed)

⚠️ Flaky E2E Tests (passed on retry)

🛠 Infra Events (absorbed by the harness)

E2E Test Summary

Uh oh!

github-actionsBot commented Aug 27, 2026

Sim World

Uh oh!

github-actionsBot commented Aug 27, 2026

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actionsBot commented Aug 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

VaguelySerious commented Aug 27, 2026•
edited
Loading

vercelBot commented Aug 27, 2026•
edited
Loading

github-actionsBot commented Aug 27, 2026•
edited
Loading

github-actionsBot commented Aug 27, 2026•
edited
Loading