Skip to content

Stop logging on healthy workflow execution - #3878

Merged
pranaygp merged 2 commits into
mainfrom
quiet-workflow-logs
Aug 28, 2026
Merged

Stop logging on healthy workflow execution#3878
pranaygp merged 2 commits into
mainfrom
quiet-workflow-logs

Conversation

@pranaygp

@pranaygppranaygp commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

What

Normal workflow execution should print nothing. Today a healthy run emits several lines that only describe the runtime working correctly.

Most of it is fallout from #3702, which defaulted the events transport to WebSockets. Three log sites written while the transport was opt-in became default-path output, because each one reports a choice the caller no longer makes:

LineWhy it was fine when WS was opt-inWhy it is noise now
world-vercel: using ws events transport (…)Confirmed the flag took effectRuns once per cold start on every deployment, naming the transport it was always going to use
…requested but a World with projectConfig … falling backA real mismatch: someone asked for WS and didn't get itNobody asks now, so every CLI command and the observability app — all projectConfig Worlds — warn about a fallback they neither chose nor can act on
…received a drain notice (reason: max_duration…)Rare while few sockets existedmax_duration and auth_expiry are routine; the transport reconnects from the close that follows and no write is lost

Swept for the same shape elsewhere and found three more:

  • world-local queue concurrency — warned per message once a fan-out exceeded the limit. That is the semaphore doing its job; every message still runs.
  • @workflow/world active-run recovery — printed on every dev-server restart with work in flight. Resuming active runs is what a restart is for.
  • @workflow/utils port detection — two diagnostics gated on NODE_ENV=development, which is the only environment that reaches this code, so the gate made them unconditional for their entire audience. The getWorkflowPort one fires on an ordinary startup race (dev server still compiling its workflow routes) that the fallback then resolves correctly.

How

A new debugLog in @workflow/utils gates on DEBUG=workflow:* (or *), the same selector @workflow/core's logger already uses, so these join world-vercel's existing httpLog and logRetry output under one switch. It reads DEBUG per call rather than at module load, since Worlds are built long after import. @workflow/world hand-rolls the same check — that package deliberately carries no workspace dependencies, matching how env-config.ts hand-rolls globalSingleton().

Nothing about error logging changed. Every console.error / console.warn on a genuine fault is untouched, including the ws-transport's "failures are never silent" set and the re-enqueue failure sitting directly above the recovery line that did get gated — that one leaves a run unresumed. logger.warn / logger.error in @workflow/core still print unconditionally.

Testing

  • packages/{utils,world,world-local,world-vercel}/src — 1449 passed, 4 skipped.
  • packages/core/src — 2268 passed (unchanged; core consumes @workflow/utils).
  • New coverage: debug-log.test.ts (off by default, accepts workflow:* / *, ignores another library's selector, re-reads per call); ws-transport tests split into DEBUG / no-DEBUG pairs; recovery tests assert a successful recovery logs at no level while a failed re-enqueue still warns without DEBUG.
  • Verified the new ws-transport assertions bite: reverting ws-transport.ts alone fails exactly 4 of them.
  • biome check on the changed files reports the same 7 pre-existing warnings as base (exit 0); turbo typecheck clean for all four packages.

Two packages/utils/src/check-data-dir.test.ts cases fail on this machine on unmodified main as well — a leftover gitignored .workflow-data at the repo root that the test walks up and finds. Unrelated to this change.

Docs

worlds/v5/vercel.mdx claimed the projectConfig fallback logs a warning once per process. Updated to say it is silent and reported under DEBUG, and to point at workflow.events.transport on the per-write span as the durable answer to which transport carried a run.

🤖 Generated with Claude Code

@vercel@pranaygp
Stop logging on healthy workflow execution
64343e9
A successful run printed several lines that described the runtime working
correctly. Most of it was fallout from defaulting the events transport to
WebSockets (#3702): three breadcrumbs written while the transport was opt-in
became default-path output, because each one reported a choice the caller no
longer makes.
- `world-vercel: using ws events transport (…)` ran once per cold start on
every deployment, naming the transport it was always going to use.
- The `projectConfig` proxy fallback warned once per process. That World cannot
hold a socket, so with WS on by default every CLI command and the
observability app warned about a fallback nobody asked for and nobody can act
on. Debug-gated and reworded from "requested but" to "unavailable for".
- The `max_duration` / `auth_expiry` drain notice is routine: the transport
reconnects from the close that follows and no write is lost.
Swept for the same shape elsewhere:
- `world-local`'s queue-concurrency notice fired per message once a fan-out
exceeded the limit — the semaphore doing its job.
- `@workflow/world`'s active-run recovery line printed on every dev-server
restart with work in flight. The re-enqueue *failure* above it stays
unconditional; that one leaves a run unresumed.
- The port-detection diagnostics in `@workflow/utils` keyed off
`NODE_ENV=development`, which is the only environment that reaches them, so
the gate made them unconditional for their whole audience.
All of it moves behind `DEBUG=workflow:*` via a new `debugLog` in
`@workflow/utils`, joining world-vercel's existing `httpLog` and `logRetry`
output under one selector. Warnings and errors are untouched, so a run that
actually goes wrong is no quieter than before — the ws-transport tests that
assert failures are never silent still pass unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp requested a review from a team as a code ownerAugust 28, 2026 01:22
@changeset-bot

changeset-botBot commented Aug 28, 2026•
edited
Loading

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 1d5f28b

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

This PR includes changesets to release 23 packages
NameType
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/utilsPatch
@workflow/worldPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/vitestPatch
@workflow/world-postgresPatch
@workflow/aiPatch
@workflow/buildersPatch
@workflow/errorsPatch
@workflow/nestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/astroPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

vercelBot commented Aug 28, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-nextjs-workflow-webpackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-astro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-express-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-fastify-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-hono-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nestjs-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nitro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nuxt-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-python-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-sveltekit-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-tanstack-start-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-vite-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-docsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-swc-playgroundReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-tarballsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-webReadyReadyPreview, v0Aug 28, 2026 3:36am

@github-actions

github-actionsBot commented Aug 28, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 1d5f28b · Fri, 28 Aug 2026 03:59:15 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep658 (+250%) 🔻1372 🔴 (+23%) 🔻1411 🔴 (+23%) 🔻1544 🔴 (+6.0%)30
TTFSstream934 (+480%) 🔻1455 🔴 (+29%) 🔻1525 🔴 (+32%) 🔻1626 🔴 (+20%) 🔻30
TTFShook + stream1720 (+44%) 🔻1812 🔴 (+31%) 🔻1844 🔴 (+27%) 🔻1982 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)714 (+9.8%)2184 (+24%) 🔻2215 (+15%) 🔻2950 (+40%) 🔻10
Fan-out TTLSPromise.all(100 steps)2155 (+15%) 🔻4016 (+8.0%)4073 (+6.9%)10458 (+51%) 🔻10
STSO1020 steps (inline)133 (+22%) 🔻153 (-3.8%)172 (-7.0%)235 (-18%) 💚1019
WO1020 steps155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)1
CRTTfirst chunk (pooled)113 (+19%) 🔻146 (-8.2%)200 (+0.5%)238 (-29%) 💚28

Streams

ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)139 (+2%)164 (-10%)265 (+7%)522 (-4%)144 (-22%)10
size sweep (100/s, 160B-12KB)137 (+5%)187 (-12%)263 (-55%)405 (-54%)119 (-44%)10
replay gateway-gpt-5.4-nano-2000t (1x)133 (-2%)149 (-16%)182 (-24%)890 (+115%)377 (+15%)3
replay eve-gpt-5.6-sol-2000t (1x)136 (-5%)155 (-16%)198 (-31%)370 (-46%)297 (-53%)2
replay eve-gpt-5.6-sol-2000t (2x)148 (-1%)214 (-15%)452 (-12%)1144 (+22%)344 (-28%)3
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 153650ms → this run 155201ms (Δ +1551ms, +1%)

100-150 ms ███████████████████████┃ main 681 this 687 +6
150-200 ms █████████░┃ main 264 this 302 +38
200-250 ms ┃█ main 52 this 23 -29
250-300 ms ┃ main 15 this 5 -10
300-350 ms ┃ main 5 this 0 -5
350-400 ms ┃ main 2 this 0 -2
400-450 ms ┃ main 0 this 2 +2
📈 CRTT drill-down vs main (RTT distributions & profiles)
variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▁▁··· 143 (-6%) 129 (-7%) 265 (+7%) 522 (-4%) 3000
sweep ······▂█▂···· 142 (-25%) 127 (-6%) 263 (-55%) 405 (-54%) 3000
gw 1x ·····▁▂█▁▁▁·· 140.4 (-6%) 127 (-5%) 182 (-24%) 890 (+115%) 5295
eve 1x ·····▁▃█▂▁··· 132.5 (-18%) 120 (-13%) 198 (-31%) 370 (-46%) 5186
eve 2x ·····▁▁█▃▁▁·· 179.4 (-19%) 150 (-14%) 452 (-12%) 1144 (+22%) 7779

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

control ██▃▃▃▁█▅▂▂ 126–164ms
sweep █▅▅▃▃▂▁▂▃▂ 120–185ms
gw 1x ▂▁▁▁▁▃▂▁▁█ 123–233ms
eve 1x ▇▅▄▄▁▄▅█▆▇ 111–148ms
eve 2x ▁▁▁▂▁▂▃█▇▂ 140–295ms

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

sweep ▁▁▃█▆▅▃ 140–145ms

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

control ▁▅▅▄▃▆█▄▇▆ 39–49ms
sweep ▁▃█▅▇▅▄▆▄▅ 43–67ms
gw 1x ▂▂▂▁▂▅▆▃▂█ 37–56ms
eve 1x █▇▃▃▁▅▄▆▃▇ 21–29ms
eve 2x ▃█▁▄▅▃▂▅▄▆ 23–31ms
📜 Previous results (1)

64343e9

Fri, 28 Aug 2026 01:46:43 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep183 (-2.7%)1314 🔴 (+18%) 🔻1383 🔴 (+20%) 🔻1480 🔴 (+1.6%)30
TTFSstream168 (+4.3%)1297 🔴 (+15%)1338 🔴 (+16%) 🔻1442 🔴 (+6.3%)30
TTFShook + stream1471 (+23%) 🔻1588 🔴 (+14%)1742 🔴 (+20%) 🔻1983 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)719 (+11%)2304 (+31%) 🔻2698 (+40%) 🔻2780 (+32%) 🔻10
Fan-out TTLSPromise.all(100 steps)1944 (+4.2%)4184 (+13%)4225 (+11%)9030 (+30%) 🔻10
STSO1020 steps (inline)101 (-7.3%)149 (-6.3%)179 (-3.2%)299 (+4.5%)1019
WO1020 steps146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)1
CRTTfirst chunk (pooled)97 (+2.1%)137 (-14%)176 (-12%)196 (-41%) 💚28

Streams

ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)122 (-10%)140 (-23%)203 (-18%)493 (-10%)114 (-38%)10
size sweep (100/s, 160B-12KB)127 (-3%)140 (-34%)195 (-67%)7053 (+695%)109 (-49%)10
replay gateway-gpt-5.4-nano-2000t (1x)119 (-12%)130 (-27%)186 (-22%)908 (+120%)224 (-32%)3
replay eve-gpt-5.6-sol-2000t (1x)124 (-14%)134 (-28%)179 (-38%)397 (-42%)331 (-48%)2
replay eve-gpt-5.6-sol-2000t (2x)176 (+17%)166 (-34%)225 (-56%)431 (-54%)231 (-51%)3
ℹ️ 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

github-actionsBot commented Aug 28, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

▲ Vercel Production (8 failed)

python-node (8 failed):

  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE | 🔍 observability
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04 | 🔍 observability
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH | 🔍 observability
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456 | 🔍 observability
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ | 🔍 observability
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD | 🔍 observability
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6 | 🔍 observability
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1 | 🔍 observability

🌐 Cross-language Conformance (9 failed)

python (9 failed):

  • deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M13767WFNN55ZPS08TTWYSE5
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1

⚠️ 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.

10 flaky tests
  • abortParallelWorkflow: abort cancels all parallel steps (nextjs-webpack)
  • addTenWorkflow (sveltekit)
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (example)
  • deploymentId: 'latest' is a no-op in non-Vercel worlds (sveltekit)
  • hookWithSleepFinalStepWorkflow - step only on final payload (nextjs-turbopack)
  • hookWorkflow (vite)
  • importMetaUrlWorkflow - import.meta.url is available in step bundles (nextjs-webpack)
  • negative startIndex (reads from end) (fastify)
  • resilient start: addTenWorkflow completes when run_created returns 500 (nextjs-webpack)
  • webhookWorkflow (nextjs-webpack)

🛠 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 (tanstack-start) · at 03:36:34Z · abandoned wrun_01M1370T9QXQY5DGPV7Z4MM7CP
  • cold-start-warmup · suite warmup (python) · at 03:37:00Z · abandoned wrun_41M136YSW40GKY4DAMXP7CRT1J · (+6 more)
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:17Z · abandoned wrun_41M1372EW50GP2RNA9ZW12DSYM
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHJ0GYNMQ8EVS4VP59M
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRH
  • run-pickup-stall · sleepingWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRG
  • run-pickup-stall · nullByteWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHY0GNNW85TFDYFH6GT
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:49Z · abandoned wrun_41M1373E6A0GJJ736KSC91PHV8
  • cold-start-warmup · suite warmup (python) · at 03:37:49Z · abandoned wrun_01M13709F0CFVSSEQJ675KSV3N · (+7 more)
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKFV76GYY90JWAWA3H9
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKMJ95Q6FMXD9S91BZG
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:38:04Z · abandoned wrun_01M1373YKE0BJMG4K9KG19CQX7
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKRHSVK59E9BRNVXXWE
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKPQN9NRWNT72VZEK34
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SV0GZC31F122EX6ZA3
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749RC0GPK46HWB57ZK200
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749VJ0GXV6SVWDJE8Z8H5
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SK0GV08Z70ZBF8ADQE
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:38:58Z · abandoned wrun_41M1374D540GRDSCRGRXRTA0VJ
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:39:04Z · abandoned wrun_01M1375S74279D328PFRY93Q2E
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7AC88CCJ5Y13RECB57
  • run-pickup-stall · sleepingWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7C45FBF9CDSBCCAF55
  • run-pickup-stall · nullByteWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7J24TG2XANEEE3438V
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7FD9PG9WVJZT46G7CB
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:04Z · abandoned wrun_01M1377KTQJY02FZSJCAAC8B4B
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:05Z · abandoned wrun_01M1377KV0R0Z2F0DH4JVMP0HS
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:05Z · abandoned wrun_01M1377KV2E6YE3WGEJJTA2ER5
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H61VC8V106V4YWDTXM3
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H6DX7Y9CPGV467FHRFT
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:48Z · abandoned wrun_41M13771MX0GS1A8AX87B70570
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:48Z · abandoned wrun_41M137751P0GQHEK8MZJP94DPC
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:41:04Z · abandoned wrun_01M1379EE7EG775GYHVRPWY4GB

E2E Test Summary

Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production357087424320
✅ 💻 Local Development392205584480
✅ 📦 Local Production392205584480
✅ 🐘 Local Postgres392205584480
✅ 🪟 Windows32000320
❌ 🌐 Cross-language Conformance09132141
✅ vercel-http-transport8170143960
✅ vercel-multi-region270027
✅ vercel-ws-transport553087640
Total1705317277819848
Details by Category

❌ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node132028
✅ astro-quickjs132028
✅ example-node132028
✅ example-quickjs132028
✅ express-node132028
✅ express-quickjs132028
✅ fastify-node132028
✅ fastify-quickjs132028
✅ hono-node132028
✅ hono-quickjs132028
✅ nest-node132028
✅ nest-quickjs132028
✅ nextjs-turbopack-node15703
✅ nextjs-turbopack-quickjs15703
✅ nextjs-webpack-node15703
✅ nextjs-webpack-quickjs15703
✅ nitro-node132028
✅ nitro-quickjs132028
✅ nuxt-node132028
✅ nuxt-quickjs132028
❌ python-node08152
✅ sveltekit-node15109
✅ sveltekit-quickjs15109
✅ tanstack-start-node132028
✅ tanstack-start-quickjs132028
✅ vite-node132028
✅ vite-quickjs132028

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node16000
✅ nextjs-turbopack-quickjs16000

❌ 🌐 Cross-language Conformance

AppPassedFailedSkipped
❌ python09132

✅ vercel-http-transport

AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ hono132028
✅ nextjs-turbopack15703
✅ nitro132028
✅ vite132028

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

✅ vercel-ws-transport

AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ nextjs-turbopack15703
✅ vite132028

📋 View full workflow run

@github-actions

github-actionsBot commented Aug 28, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor

Sim World

Simulated world deterministic testing for races. Traces

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

fence=per-spec

scenariooutcomeeventsvirtreplayviolations
✅ smoke-no-stepscompleted30msok0
✅ smoke-one-stepcompleted60msok0
✅ hook-at-step-startedcompleted120msok0
✅ hook-at-step-completedcompleted120msok0
✅ hook-at-hook-createdcompleted120msok0
✅ deadline-hook-winscompleted71.0hok0
✅ deadline-expirescompleted71.0hok0
✅ long-sleepcompleted1130.0dok0
✅ hook-never-arrivesstalled30msskipped0
✅ step-retries-twicecompleted102.0sok0
✅ parallel-stepscompleted90msok0
✅ hook-on-execution-statecompleted120msok0
✅ peek-hook-before-branchcompleted120msok0
✅ peek-hook-after-branchcompleted120msok0
✅ peek-hook-at-registrationcompleted120msok0
✅ race-hook-before-probecompleted120msok0
✅ race-hook-after-probecompleted120msok0
✅ race-duplicate-deliverycompleted130msok0
✅ attr-hook-before-stepcompleted110msok0
✅ attr-hook-after-stepcompleted110msok0
✅ attr-from-step-bodycompleted130msok0
✅ fork-hook-after-timeoutcompleted141.0mok0
✅ fork-hook-before-timeoutcompleted141.0mok0
✅ count-hook-after-timeoutcompleted171.0mok0
✅ count-hook-before-timeoutcompleted201.0mok0
✅ stale-read-step-count-forkcompleted201.0mok0
✅ stale-read-equal-step-countscompleted141.0mok0
✅ step-vs-step-forkcompleted120msok0
✅ step-vs-step-fork-fencedcompleted120msok0
✅ fence-catches-benign-directioncompleted125msok0
✅ in-flight-before-decisioncompleted171.0mok0
❌ in-flight-before-decision-countedcompleted171.0mok0
✅ in-flight-after-decisioncompleted192.0mok0
✅ stale-read-step-count-fork-fencedcompleted201.0mok0
✅ fork-hook-winscompleted131.0mok0
✅ fork-timeout-winscompleted131.0mok0
✅ unclaimed-payload-under-forkcompleted171.0mok0
✅ claimed-payload-under-forkcompleted171.0mok0
✅ writers-independent-step-bodiescompleted120msok0
✅ writers-scripted-tempocompleted120msok0
✅ cancel-mid-stepcancelled70msskipped0

Full trace: world-sim.txt

@github-actions

github-actionsBot commented Aug 28, 2026•
edited
Loading

Copy link
Copy Markdown
Contributor
FrameworkFlow routeStep reg.Framework output
hono200.9 KiB (±0)40.3 KiB (+27 B)1.76 MiB (+753 B)
nextjs-turbopack206.3 KiB (±0)439 B (±0)763.7 KiB (+206 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.

1d5f28b · run

shalabhc
shalabhc approved these changes Aug 28, 2026
View reviewed changes

@shalabhcshalabhc left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

changeset looks too large tho

pranaygp
pranaygp commented Aug 28, 2026
View reviewed changes
Comment thread.changeset/quiet-normal-execution-logs.md Outdated
'@workflow/world': patch
---

Stop logging on healthy workflow execution. A successful run now prints nothing;

@pranaygppranaygpAug 28, 2026

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

make this more terse (see the other changlogs. should just be one-two line. not a story)

@pranaygppranaygpAug 28, 2026

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Trimmed to two sentences in 1d5f28b — matches the AGENTS.md guidance (one sentence, two at most) and the length of the other changelogs. The per-log-site rationale stays in the PR description. Package list and bump types are unchanged.

pranaygp
pranaygp commented Aug 28, 2026
View reviewed changes
Comment threadpackages/world-local/src/queue.ts
// Debug-gated: this is the semaphore doing its job. A fan-out wider
// than the limit queues behind it and every message still runs, so a
// per-message warning turns a healthy wide run into a wall of output.
debugLog(

@pranaygppranaygpAug 28, 2026

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

nice fix!

@vercel@pranaygp
Trim the changeset to two sentences
1d5f28b
Review feedback: the changeset read as a story. AGENTS.md asks for one
sentence, or two at most; the per-log-site rationale already lives in the
PR description. Package list and bump types are unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp merged commit ffc5807 into mainAug 28, 2026
181 of 183 checks passed
@pranaygp
pranaygp deleted the quiet-workflow-logs branch August 28, 2026 03:45
@github-actions

github-actionsBot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

No backport to stable for ffc5807 (AI decision).

This is log-noise cleanup, not a stability fix: it changes existing logging behavior (warn/log downgraded to a DEBUG-gated debug line) and adds new public API surface (debugLog / isWorkflowDebugEnabled exported from @workflow/utils), with no correctness, crash, or resource issue being fixed. Its stated motivation is also largely main-only — packages/world-vercel/src/ws-transport.ts and docs/content/worlds/ do not exist on origin/stable, so the WebSocket-default fallout that drove the change does not affect the maintenance line. The residual bits that do apply on stable (packages/utils/src/get-port.ts, packages/world-local/src/queue.ts, packages/world/src/recovery.ts) are cosmetic verbosity changes that stable users can live without.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

ffc58078d0c3cd2786d69bab7e41614566a9ea4e

This was referenced Aug 28, 2026
Open
Open
Open
Open
Open
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@shalabhcshalabhcshalabhc approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@pranaygp@shalabhc
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Stop logging on healthy workflow execution by pranaygp · Pull Request #3878 · vercel/workflow · GitHub
Skip to content
Stop logging on healthy workflow execution - #3878
Merged
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Aug 28, 2026
Merged
Stop logging on healthy workflow execution#3878
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Conversation
@pranaygp
@pranaygppranaygp
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
What
Normal workflow execution should print nothing. Today a healthy run emits several lines that only describe the runtime working correctly.
Most of it is fallout from #3702, which defaulted the events transport to WebSockets. Three log sites written while the transport was opt-in became default-path output, because each one reports a choice the caller no longer makes:
LineWhy it was fine when WS was opt-inWhy it is noise now
world-vercel: using ws events transport (…)Confirmed the flag took effectRuns once per cold start on every deployment, naming the transport it was always going to use
…requested but a World with projectConfig … falling backA real mismatch: someone asked for WS and didn't get itNobody asks now, so every CLI command and the observability app — all projectConfig Worlds — warn about a fallback they neither chose nor can act on
…received a drain notice (reason: max_duration…)Rare while few sockets existedmax_duration and auth_expiry are routine; the transport reconnects from the close that follows and no write is lost
Swept for the same shape elsewhere and found three more:
  • world-local queue concurrency — warned per message once a fan-out exceeded the limit. That is the semaphore doing its job; every message still runs.
  • @workflow/world active-run recovery — printed on every dev-server restart with work in flight. Resuming active runs is what a restart is for.
  • @workflow/utils port detection — two diagnostics gated on NODE_ENV=development, which is the only environment that reaches this code, so the gate made them unconditional for their entire audience. The getWorkflowPort one fires on an ordinary startup race (dev server still compiling its workflow routes) that the fallback then resolves correctly.
How
A new debugLog in @workflow/utils gates on DEBUG=workflow:* (or *), the same selector @workflow/core's logger already uses, so these join world-vercel's existing httpLog and logRetry output under one switch. It reads DEBUG per call rather than at module load, since Worlds are built long after import. @workflow/world hand-rolls the same check — that package deliberately carries no workspace dependencies, matching how env-config.ts hand-rolls globalSingleton().
Nothing about error logging changed. Every console.error / console.warn on a genuine fault is untouched, including the ws-transport's "failures are never silent" set and the re-enqueue failure sitting directly above the recovery line that did get gated — that one leaves a run unresumed. logger.warn / logger.error in @workflow/core still print unconditionally.
Testing
  • packages/{utils,world,world-local,world-vercel}/src — 1449 passed, 4 skipped.
  • packages/core/src — 2268 passed (unchanged; core consumes @workflow/utils).
  • New coverage: debug-log.test.ts (off by default, accepts workflow:* / *, ignores another library's selector, re-reads per call); ws-transport tests split into DEBUG / no-DEBUG pairs; recovery tests assert a successful recovery logs at no level while a failed re-enqueue still warns without DEBUG.
  • Verified the new ws-transport assertions bite: reverting ws-transport.ts alone fails exactly 4 of them.
  • biome check on the changed files reports the same 7 pre-existing warnings as base (exit 0); turbo typecheck clean for all four packages.
Two packages/utils/src/check-data-dir.test.ts cases fail on this machine on unmodified main as well — a leftover gitignored .workflow-data at the repo root that the test walks up and finds. Unrelated to this change.
Docs
worlds/v5/vercel.mdx claimed the projectConfig fallback logs a warning once per process. Updated to say it is silent and reported under DEBUG, and to point at workflow.events.transport on the per-write span as the durable answer to which transport carried a run.
🤖 Generated with Claude Code
@vercel@pranaygp
Stop logging on healthy workflow execution
64343e9
A successful run printed several lines that described the runtime working
correctly. Most of it was fallout from defaulting the events transport to
WebSockets (#3702): three breadcrumbs written while the transport was opt-in
became default-path output, because each one reported a choice the caller no
longer makes.
- `world-vercel: using ws events transport (…)` ran once per cold start on
every deployment, naming the transport it was always going to use.
- The `projectConfig` proxy fallback warned once per process. That World cannot
hold a socket, so with WS on by default every CLI command and the
observability app warned about a fallback nobody asked for and nobody can act
on. Debug-gated and reworded from "requested but" to "unavailable for".
- The `max_duration` / `auth_expiry` drain notice is routine: the transport
reconnects from the close that follows and no write is lost.
Swept for the same shape elsewhere:
- `world-local`'s queue-concurrency notice fired per message once a fan-out
exceeded the limit — the semaphore doing its job.
- `@workflow/world`'s active-run recovery line printed on every dev-server
restart with work in flight. The re-enqueue *failure* above it stays
unconditional; that one leaves a run unresumed.
- The port-detection diagnostics in `@workflow/utils` keyed off
`NODE_ENV=development`, which is the only environment that reaches them, so
the gate made them unconditional for their whole audience.
All of it moves behind `DEBUG=workflow:*` via a new `debugLog` in
`@workflow/utils`, joining world-vercel's existing `httpLog` and `logRetry`
output under one selector. Warnings and errors are untouched, so a run that
actually goes wrong is no quieter than before — the ws-transport tests that
assert failures are never silent still pass unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
requested a review
from a team
as a code ownerAugust 28, 2026 01:22
@changeset-bot
changeset-botBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 1d5f28b
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 23 packages
NameType
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/utilsPatch
@workflow/worldPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/vitestPatch
@workflow/world-postgresPatch
@workflow/aiPatch
@workflow/buildersPatch
@workflow/errorsPatch
@workflow/nestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/astroPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
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
vercelBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-nextjs-workflow-webpackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-astro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-express-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-fastify-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-hono-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nestjs-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nitro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nuxt-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-python-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-sveltekit-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-tanstack-start-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-vite-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-docsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-swc-playgroundReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-tarballsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-webReadyReadyPreview, v0Aug 28, 2026 3:36am
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
📊 Workflow Benchmarks
commit 1d5f28b · Fri, 28 Aug 2026 03:59:15 GMT · run logs
Backend: vercel · app: nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep658 (+250%) 🔻1372 🔴 (+23%) 🔻1411 🔴 (+23%) 🔻1544 🔴 (+6.0%)30
TTFSstream934 (+480%) 🔻1455 🔴 (+29%) 🔻1525 🔴 (+32%) 🔻1626 🔴 (+20%) 🔻30
TTFShook + stream1720 (+44%) 🔻1812 🔴 (+31%) 🔻1844 🔴 (+27%) 🔻1982 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)714 (+9.8%)2184 (+24%) 🔻2215 (+15%) 🔻2950 (+40%) 🔻10
Fan-out TTLSPromise.all(100 steps)2155 (+15%) 🔻4016 (+8.0%)4073 (+6.9%)10458 (+51%) 🔻10
STSO1020 steps (inline)133 (+22%) 🔻153 (-3.8%)172 (-7.0%)235 (-18%) 💚1019
WO1020 steps155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)1
CRTTfirst chunk (pooled)113 (+19%) 🔻146 (-8.2%)200 (+0.5%)238 (-29%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)139 (+2%)164 (-10%)265 (+7%)522 (-4%)144 (-22%)10
size sweep (100/s, 160B-12KB)137 (+5%)187 (-12%)263 (-55%)405 (-54%)119 (-44%)10
replay gateway-gpt-5.4-nano-2000t (1x)133 (-2%)149 (-16%)182 (-24%)890 (+115%)377 (+15%)3
replay eve-gpt-5.6-sol-2000t (1x)136 (-5%)155 (-16%)198 (-31%)370 (-46%)297 (-53%)2
replay eve-gpt-5.6-sol-2000t (2x)148 (-1%)214 (-15%)452 (-12%)1144 (+22%)344 (-28%)3
📈 STSO distribution vs main (inline / queue-hop histograms)
1020 steps (inline)
Cumulative STSO time: main 153650ms → this run 155201ms (Δ +1551ms, +1%)
100-150 ms ███████████████████████┃ main 681 this 687 +6
150-200 ms █████████░┃ main 264 this 302 +38
200-250 ms ┃█ main 52 this 23 -29
250-300 ms ┃ main 15 this 5 -10
300-350 ms ┃ main 5 this 0 -5
350-400 ms ┃ main 2 this 0 -2
400-450 ms ┃ main 0 this 2 +2

📈 CRTT drill-down vs main (RTT distributions & profiles)
variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▁▁··· 143 (-6%) 129 (-7%) 265 (+7%) 522 (-4%) 3000
sweep ······▂█▂···· 142 (-25%) 127 (-6%) 263 (-55%) 405 (-54%) 3000
gw 1x ·····▁▂█▁▁▁·· 140.4 (-6%) 127 (-5%) 182 (-24%) 890 (+115%) 5295
eve 1x ·····▁▃█▂▁··· 132.5 (-18%) 120 (-13%) 198 (-31%) 370 (-46%) 5186
eve 2x ·····▁▁█▃▁▁·· 179.4 (-19%) 150 (-14%) 452 (-12%) 1144 (+22%) 7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):
control ██▃▃▃▁█▅▂▂ 126–164ms
sweep █▅▅▃▃▂▁▂▃▂ 120–185ms
gw 1x ▂▁▁▁▁▃▂▁▁█ 123–233ms
eve 1x ▇▅▄▄▁▄▅█▆▇ 111–148ms
eve 2x ▁▁▁▂▁▂▃█▇▂ 140–295ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):
sweep ▁▁▃█▆▅▃ 140–145ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):
control ▁▅▅▄▃▆█▄▇▆ 39–49ms
sweep ▁▃█▅▇▅▄▆▄▅ 43–67ms
gw 1x ▂▂▂▁▂▅▆▃▂█ 37–56ms
eve 1x █▇▃▃▁▅▄▆▃▇ 21–29ms
eve 2x ▃█▁▄▅▃▂▅▄▆ 23–31ms

📜 Previous results (1)
64343e9
Fri, 28 Aug 2026 01:46:43 GMT · run logs
vercel / nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep183 (-2.7%)1314 🔴 (+18%) 🔻1383 🔴 (+20%) 🔻1480 🔴 (+1.6%)30
TTFSstream168 (+4.3%)1297 🔴 (+15%)1338 🔴 (+16%) 🔻1442 🔴 (+6.3%)30
TTFShook + stream1471 (+23%) 🔻1588 🔴 (+14%)1742 🔴 (+20%) 🔻1983 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)719 (+11%)2304 (+31%) 🔻2698 (+40%) 🔻2780 (+32%) 🔻10
Fan-out TTLSPromise.all(100 steps)1944 (+4.2%)4184 (+13%)4225 (+11%)9030 (+30%) 🔻10
STSO1020 steps (inline)101 (-7.3%)149 (-6.3%)179 (-3.2%)299 (+4.5%)1019
WO1020 steps146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)1
CRTTfirst chunk (pooled)97 (+2.1%)137 (-14%)176 (-12%)196 (-41%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)122 (-10%)140 (-23%)203 (-18%)493 (-10%)114 (-38%)10
size sweep (100/s, 160B-12KB)127 (-3%)140 (-34%)195 (-67%)7053 (+695%)109 (-49%)10
replay gateway-gpt-5.4-nano-2000t (1x)119 (-12%)130 (-27%)186 (-22%)908 (+120%)224 (-32%)3
replay eve-gpt-5.6-sol-2000t (1x)124 (-14%)134 (-28%)179 (-38%)397 (-42%)331 (-48%)2
replay eve-gpt-5.6-sol-2000t (2x)176 (+17%)166 (-34%)225 (-56%)431 (-54%)231 (-51%)3
ℹ️ 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
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
❌ Failed E2E Tests
▲ Vercel Production (8 failed)
python-node (8 failed):
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE | 🔍 observability
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04 | 🔍 observability
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH | 🔍 observability
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456 | 🔍 observability
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ | 🔍 observability
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD | 🔍 observability
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6 | 🔍 observability
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1 | 🔍 observability
🌐 Cross-language Conformance (9 failed)
python (9 failed):
  • deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M13767WFNN55ZPS08TTWYSE5
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1
⚠️ 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.
10 flaky tests
  • abortParallelWorkflow: abort cancels all parallel steps (nextjs-webpack)
  • addTenWorkflow (sveltekit)
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (example)
  • deploymentId: 'latest' is a no-op in non-Vercel worlds (sveltekit)
  • hookWithSleepFinalStepWorkflow - step only on final payload (nextjs-turbopack)
  • hookWorkflow (vite)
  • importMetaUrlWorkflow - import.meta.url is available in step bundles (nextjs-webpack)
  • negative startIndex (reads from end) (fastify)
  • resilient start: addTenWorkflow completes when run_created returns 500 (nextjs-webpack)
  • webhookWorkflow (nextjs-webpack)
🛠 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 (tanstack-start) · at 03:36:34Z · abandoned wrun_01M1370T9QXQY5DGPV7Z4MM7CP
  • cold-start-warmup · suite warmup (python) · at 03:37:00Z · abandoned wrun_41M136YSW40GKY4DAMXP7CRT1J · (+6 more)
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:17Z · abandoned wrun_41M1372EW50GP2RNA9ZW12DSYM
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHJ0GYNMQ8EVS4VP59M
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRH
  • run-pickup-stall · sleepingWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRG
  • run-pickup-stall · nullByteWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHY0GNNW85TFDYFH6GT
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:49Z · abandoned wrun_41M1373E6A0GJJ736KSC91PHV8
  • cold-start-warmup · suite warmup (python) · at 03:37:49Z · abandoned wrun_01M13709F0CFVSSEQJ675KSV3N · (+7 more)
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKFV76GYY90JWAWA3H9
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKMJ95Q6FMXD9S91BZG
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:38:04Z · abandoned wrun_01M1373YKE0BJMG4K9KG19CQX7
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKRHSVK59E9BRNVXXWE
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKPQN9NRWNT72VZEK34
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SV0GZC31F122EX6ZA3
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749RC0GPK46HWB57ZK200
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749VJ0GXV6SVWDJE8Z8H5
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SK0GV08Z70ZBF8ADQE
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:38:58Z · abandoned wrun_41M1374D540GRDSCRGRXRTA0VJ
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:39:04Z · abandoned wrun_01M1375S74279D328PFRY93Q2E
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7AC88CCJ5Y13RECB57
  • run-pickup-stall · sleepingWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7C45FBF9CDSBCCAF55
  • run-pickup-stall · nullByteWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7J24TG2XANEEE3438V
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7FD9PG9WVJZT46G7CB
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:04Z · abandoned wrun_01M1377KTQJY02FZSJCAAC8B4B
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:05Z · abandoned wrun_01M1377KV0R0Z2F0DH4JVMP0HS
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:05Z · abandoned wrun_01M1377KV2E6YE3WGEJJTA2ER5
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H61VC8V106V4YWDTXM3
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H6DX7Y9CPGV467FHRFT
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:48Z · abandoned wrun_41M13771MX0GS1A8AX87B70570
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:48Z · abandoned wrun_41M137751P0GQHEK8MZJP94DPC
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:41:04Z · abandoned wrun_01M1379EE7EG775GYHVRPWY4GB
E2E Test Summary
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production357087424320
✅ 💻 Local Development392205584480
✅ 📦 Local Production392205584480
✅ 🐘 Local Postgres392205584480
✅ 🪟 Windows32000320
❌ 🌐 Cross-language Conformance09132141
✅ vercel-http-transport8170143960
✅ vercel-multi-region270027
✅ vercel-ws-transport553087640
Total1705317277819848
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro-node132028
✅ astro-quickjs132028
✅ example-node132028
✅ example-quickjs132028
✅ express-node132028
✅ express-quickjs132028
✅ fastify-node132028
✅ fastify-quickjs132028
✅ hono-node132028
✅ hono-quickjs132028
✅ nest-node132028
✅ nest-quickjs132028
✅ nextjs-turbopack-node15703
✅ nextjs-turbopack-quickjs15703
✅ nextjs-webpack-node15703
✅ nextjs-webpack-quickjs15703
✅ nitro-node132028
✅ nitro-quickjs132028
✅ nuxt-node132028
✅ nuxt-quickjs132028
❌ python-node08152
✅ sveltekit-node15109
✅ sveltekit-quickjs15109
✅ tanstack-start-node132028
✅ tanstack-start-quickjs132028
✅ vite-node132028
✅ vite-quickjs132028
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack-node16000
✅ nextjs-turbopack-quickjs16000
❌ 🌐 Cross-language Conformance
AppPassedFailedSkipped
❌ python09132
✅ vercel-http-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ hono132028
✅ nextjs-turbopack15703
✅ nitro132028
✅ vite132028
✅ vercel-multi-region
AppPassedFailedSkipped
✅ nextjs-turbopack2700
✅ vercel-ws-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ nextjs-turbopack15703
✅ vite132028
📋 View full workflow run
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Sim World
Simulated world deterministic testing for races. Traces
🟠 world-sim scenario book — 1 fail of 41 total
fence=per-spec
scenariooutcomeeventsvirtreplayviolations
✅ smoke-no-stepscompleted30msok0
✅ smoke-one-stepcompleted60msok0
✅ hook-at-step-startedcompleted120msok0
✅ hook-at-step-completedcompleted120msok0
✅ hook-at-hook-createdcompleted120msok0
✅ deadline-hook-winscompleted71.0hok0
✅ deadline-expirescompleted71.0hok0
✅ long-sleepcompleted1130.0dok0
✅ hook-never-arrivesstalled30msskipped0
✅ step-retries-twicecompleted102.0sok0
✅ parallel-stepscompleted90msok0
✅ hook-on-execution-statecompleted120msok0
✅ peek-hook-before-branchcompleted120msok0
✅ peek-hook-after-branchcompleted120msok0
✅ peek-hook-at-registrationcompleted120msok0
✅ race-hook-before-probecompleted120msok0
✅ race-hook-after-probecompleted120msok0
✅ race-duplicate-deliverycompleted130msok0
✅ attr-hook-before-stepcompleted110msok0
✅ attr-hook-after-stepcompleted110msok0
✅ attr-from-step-bodycompleted130msok0
✅ fork-hook-after-timeoutcompleted141.0mok0
✅ fork-hook-before-timeoutcompleted141.0mok0
✅ count-hook-after-timeoutcompleted171.0mok0
✅ count-hook-before-timeoutcompleted201.0mok0
✅ stale-read-step-count-forkcompleted201.0mok0
✅ stale-read-equal-step-countscompleted141.0mok0
✅ step-vs-step-forkcompleted120msok0
✅ step-vs-step-fork-fencedcompleted120msok0
✅ fence-catches-benign-directioncompleted125msok0
✅ in-flight-before-decisioncompleted171.0mok0
❌ in-flight-before-decision-countedcompleted171.0mok0
✅ in-flight-after-decisioncompleted192.0mok0
✅ stale-read-step-count-fork-fencedcompleted201.0mok0
✅ fork-hook-winscompleted131.0mok0
✅ fork-timeout-winscompleted131.0mok0
✅ unclaimed-payload-under-forkcompleted171.0mok0
✅ claimed-payload-under-forkcompleted171.0mok0
✅ writers-independent-step-bodiescompleted120msok0
✅ writers-scripted-tempocompleted120msok0
✅ cancel-mid-stepcancelled70msskipped0
Full trace: world-sim.txt
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
FrameworkFlow routeStep reg.Framework output
hono200.9 KiB (±0)40.3 KiB (+27 B)1.76 MiB (+753 B)
nextjs-turbopack206.3 KiB (±0)439 B (±0)763.7 KiB (+206 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.
1d5f28b · run
shalabhc
shalabhc
approved these changes
Aug 28, 2026
View reviewed changes
@shalabhcshalabhc
left a comment


Copy link


Copy Markdown

Collaborator
Choose a reason for hiding this comment

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

changeset looks too large tho
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment thread.changeset/quiet-normal-execution-logs.md
Outdated

'@workflow/world': patch
---

Stop logging on healthy workflow execution. A successful run now prints nothing;
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

make this more terse (see the other changlogs. should just be one-two line. not a story)
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

Trimmed to two sentences in 1d5f28b — matches the AGENTS.md guidance (one sentence, two at most) and the length of the other changelogs. The per-log-site rationale stays in the PR description. Package list and bump types are unchanged.
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment threadpackages/world-local/src/queue.ts
 // Debug-gated: this is the semaphore doing its job. A fan-out wider
 // than the limit queues behind it and every message still runs, so a
 // per-message warning turns a healthy wide run into a wall of output.
 debugLog(
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

nice fix!
@vercel@pranaygp
Trim the changeset to two sentences
1d5f28b
Review feedback: the changeset read as a story. AGENTS.md asks for one
sentence, or two at most; the per-log-site rationale already lives in the
PR description. Package list and bump types are unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
merged commit ffc5807
into
mainAug 28, 2026

181 of 183 checks passed

@pranaygp
pranaygp
deleted the

quiet-workflow-logs

branch
August 28, 2026 03:45
@github-actions
github-actionsBot
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
No backport to stable for ffc5807 (AI decision).
This is log-noise cleanup, not a stability fix: it changes existing logging behavior (warn/log downgraded to a DEBUG-gated debug line) and adds new public API surface (debugLog / isWorkflowDebugEnabled exported from @workflow/utils), with no correctness, crash, or resource issue being fixed. Its stated motivation is also largely main-only — packages/world-vercel/src/ws-transport.ts and docs/content/worlds/ do not exist on origin/stable, so the WebSocket-default fallout that drove the change does not affect the maintenance line. The residual bits that do apply on stable (packages/utils/src/get-port.ts, packages/world-local/src/queue.ts, packages/world/src/recovery.ts) are cosmetic verbosity changes that stable users can live without.
To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:
ffc58078d0c3cd2786d69bab7e41614566a9ea4e


This was referenced Aug 28, 2026
 Open

 Open

 Open

 Open

 Open

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

Reviewers

@shalabhcshalabhcshalabhc approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@pranaygp@shalabhc

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Stop logging on healthy workflow execution by pranaygp · Pull Request #3878 · vercel/workflow · GitHub
Skip to content
Stop logging on healthy workflow execution - #3878
Merged
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Aug 28, 2026
Merged
Stop logging on healthy workflow execution#3878
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Conversation
@pranaygp
@pranaygppranaygp
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
What
Normal workflow execution should print nothing. Today a healthy run emits several lines that only describe the runtime working correctly.
Most of it is fallout from #3702, which defaulted the events transport to WebSockets. Three log sites written while the transport was opt-in became default-path output, because each one reports a choice the caller no longer makes:
LineWhy it was fine when WS was opt-inWhy it is noise now
world-vercel: using ws events transport (…)Confirmed the flag took effectRuns once per cold start on every deployment, naming the transport it was always going to use
…requested but a World with projectConfig … falling backA real mismatch: someone asked for WS and didn't get itNobody asks now, so every CLI command and the observability app — all projectConfig Worlds — warn about a fallback they neither chose nor can act on
…received a drain notice (reason: max_duration…)Rare while few sockets existedmax_duration and auth_expiry are routine; the transport reconnects from the close that follows and no write is lost
Swept for the same shape elsewhere and found three more:
  • world-local queue concurrency — warned per message once a fan-out exceeded the limit. That is the semaphore doing its job; every message still runs.
  • @workflow/world active-run recovery — printed on every dev-server restart with work in flight. Resuming active runs is what a restart is for.
  • @workflow/utils port detection — two diagnostics gated on NODE_ENV=development, which is the only environment that reaches this code, so the gate made them unconditional for their entire audience. The getWorkflowPort one fires on an ordinary startup race (dev server still compiling its workflow routes) that the fallback then resolves correctly.
How
A new debugLog in @workflow/utils gates on DEBUG=workflow:* (or *), the same selector @workflow/core's logger already uses, so these join world-vercel's existing httpLog and logRetry output under one switch. It reads DEBUG per call rather than at module load, since Worlds are built long after import. @workflow/world hand-rolls the same check — that package deliberately carries no workspace dependencies, matching how env-config.ts hand-rolls globalSingleton().
Nothing about error logging changed. Every console.error / console.warn on a genuine fault is untouched, including the ws-transport's "failures are never silent" set and the re-enqueue failure sitting directly above the recovery line that did get gated — that one leaves a run unresumed. logger.warn / logger.error in @workflow/core still print unconditionally.
Testing
  • packages/{utils,world,world-local,world-vercel}/src — 1449 passed, 4 skipped.
  • packages/core/src — 2268 passed (unchanged; core consumes @workflow/utils).
  • New coverage: debug-log.test.ts (off by default, accepts workflow:* / *, ignores another library's selector, re-reads per call); ws-transport tests split into DEBUG / no-DEBUG pairs; recovery tests assert a successful recovery logs at no level while a failed re-enqueue still warns without DEBUG.
  • Verified the new ws-transport assertions bite: reverting ws-transport.ts alone fails exactly 4 of them.
  • biome check on the changed files reports the same 7 pre-existing warnings as base (exit 0); turbo typecheck clean for all four packages.
Two packages/utils/src/check-data-dir.test.ts cases fail on this machine on unmodified main as well — a leftover gitignored .workflow-data at the repo root that the test walks up and finds. Unrelated to this change.
Docs
worlds/v5/vercel.mdx claimed the projectConfig fallback logs a warning once per process. Updated to say it is silent and reported under DEBUG, and to point at workflow.events.transport on the per-write span as the durable answer to which transport carried a run.
🤖 Generated with Claude Code
@vercel@pranaygp
Stop logging on healthy workflow execution
64343e9
A successful run printed several lines that described the runtime working
correctly. Most of it was fallout from defaulting the events transport to
WebSockets (#3702): three breadcrumbs written while the transport was opt-in
became default-path output, because each one reported a choice the caller no
longer makes.
- `world-vercel: using ws events transport (…)` ran once per cold start on
every deployment, naming the transport it was always going to use.
- The `projectConfig` proxy fallback warned once per process. That World cannot
hold a socket, so with WS on by default every CLI command and the
observability app warned about a fallback nobody asked for and nobody can act
on. Debug-gated and reworded from "requested but" to "unavailable for".
- The `max_duration` / `auth_expiry` drain notice is routine: the transport
reconnects from the close that follows and no write is lost.
Swept for the same shape elsewhere:
- `world-local`'s queue-concurrency notice fired per message once a fan-out
exceeded the limit — the semaphore doing its job.
- `@workflow/world`'s active-run recovery line printed on every dev-server
restart with work in flight. The re-enqueue *failure* above it stays
unconditional; that one leaves a run unresumed.
- The port-detection diagnostics in `@workflow/utils` keyed off
`NODE_ENV=development`, which is the only environment that reaches them, so
the gate made them unconditional for their whole audience.
All of it moves behind `DEBUG=workflow:*` via a new `debugLog` in
`@workflow/utils`, joining world-vercel's existing `httpLog` and `logRetry`
output under one selector. Warnings and errors are untouched, so a run that
actually goes wrong is no quieter than before — the ws-transport tests that
assert failures are never silent still pass unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
requested a review
from a team
as a code ownerAugust 28, 2026 01:22
@changeset-bot
changeset-botBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 1d5f28b
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 23 packages
NameType
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/utilsPatch
@workflow/worldPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/vitestPatch
@workflow/world-postgresPatch
@workflow/aiPatch
@workflow/buildersPatch
@workflow/errorsPatch
@workflow/nestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/astroPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
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
vercelBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-nextjs-workflow-webpackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-astro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-express-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-fastify-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-hono-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nestjs-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nitro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nuxt-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-python-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-sveltekit-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-tanstack-start-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-vite-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-docsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-swc-playgroundReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-tarballsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-webReadyReadyPreview, v0Aug 28, 2026 3:36am
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
📊 Workflow Benchmarks
commit 1d5f28b · Fri, 28 Aug 2026 03:59:15 GMT · run logs
Backend: vercel · app: nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep658 (+250%) 🔻1372 🔴 (+23%) 🔻1411 🔴 (+23%) 🔻1544 🔴 (+6.0%)30
TTFSstream934 (+480%) 🔻1455 🔴 (+29%) 🔻1525 🔴 (+32%) 🔻1626 🔴 (+20%) 🔻30
TTFShook + stream1720 (+44%) 🔻1812 🔴 (+31%) 🔻1844 🔴 (+27%) 🔻1982 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)714 (+9.8%)2184 (+24%) 🔻2215 (+15%) 🔻2950 (+40%) 🔻10
Fan-out TTLSPromise.all(100 steps)2155 (+15%) 🔻4016 (+8.0%)4073 (+6.9%)10458 (+51%) 🔻10
STSO1020 steps (inline)133 (+22%) 🔻153 (-3.8%)172 (-7.0%)235 (-18%) 💚1019
WO1020 steps155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)1
CRTTfirst chunk (pooled)113 (+19%) 🔻146 (-8.2%)200 (+0.5%)238 (-29%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)139 (+2%)164 (-10%)265 (+7%)522 (-4%)144 (-22%)10
size sweep (100/s, 160B-12KB)137 (+5%)187 (-12%)263 (-55%)405 (-54%)119 (-44%)10
replay gateway-gpt-5.4-nano-2000t (1x)133 (-2%)149 (-16%)182 (-24%)890 (+115%)377 (+15%)3
replay eve-gpt-5.6-sol-2000t (1x)136 (-5%)155 (-16%)198 (-31%)370 (-46%)297 (-53%)2
replay eve-gpt-5.6-sol-2000t (2x)148 (-1%)214 (-15%)452 (-12%)1144 (+22%)344 (-28%)3
📈 STSO distribution vs main (inline / queue-hop histograms)
1020 steps (inline)
Cumulative STSO time: main 153650ms → this run 155201ms (Δ +1551ms, +1%)
100-150 ms ███████████████████████┃ main 681 this 687 +6
150-200 ms █████████░┃ main 264 this 302 +38
200-250 ms ┃█ main 52 this 23 -29
250-300 ms ┃ main 15 this 5 -10
300-350 ms ┃ main 5 this 0 -5
350-400 ms ┃ main 2 this 0 -2
400-450 ms ┃ main 0 this 2 +2

📈 CRTT drill-down vs main (RTT distributions & profiles)
variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▁▁··· 143 (-6%) 129 (-7%) 265 (+7%) 522 (-4%) 3000
sweep ······▂█▂···· 142 (-25%) 127 (-6%) 263 (-55%) 405 (-54%) 3000
gw 1x ·····▁▂█▁▁▁·· 140.4 (-6%) 127 (-5%) 182 (-24%) 890 (+115%) 5295
eve 1x ·····▁▃█▂▁··· 132.5 (-18%) 120 (-13%) 198 (-31%) 370 (-46%) 5186
eve 2x ·····▁▁█▃▁▁·· 179.4 (-19%) 150 (-14%) 452 (-12%) 1144 (+22%) 7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):
control ██▃▃▃▁█▅▂▂ 126–164ms
sweep █▅▅▃▃▂▁▂▃▂ 120–185ms
gw 1x ▂▁▁▁▁▃▂▁▁█ 123–233ms
eve 1x ▇▅▄▄▁▄▅█▆▇ 111–148ms
eve 2x ▁▁▁▂▁▂▃█▇▂ 140–295ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):
sweep ▁▁▃█▆▅▃ 140–145ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):
control ▁▅▅▄▃▆█▄▇▆ 39–49ms
sweep ▁▃█▅▇▅▄▆▄▅ 43–67ms
gw 1x ▂▂▂▁▂▅▆▃▂█ 37–56ms
eve 1x █▇▃▃▁▅▄▆▃▇ 21–29ms
eve 2x ▃█▁▄▅▃▂▅▄▆ 23–31ms

📜 Previous results (1)
64343e9
Fri, 28 Aug 2026 01:46:43 GMT · run logs
vercel / nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep183 (-2.7%)1314 🔴 (+18%) 🔻1383 🔴 (+20%) 🔻1480 🔴 (+1.6%)30
TTFSstream168 (+4.3%)1297 🔴 (+15%)1338 🔴 (+16%) 🔻1442 🔴 (+6.3%)30
TTFShook + stream1471 (+23%) 🔻1588 🔴 (+14%)1742 🔴 (+20%) 🔻1983 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)719 (+11%)2304 (+31%) 🔻2698 (+40%) 🔻2780 (+32%) 🔻10
Fan-out TTLSPromise.all(100 steps)1944 (+4.2%)4184 (+13%)4225 (+11%)9030 (+30%) 🔻10
STSO1020 steps (inline)101 (-7.3%)149 (-6.3%)179 (-3.2%)299 (+4.5%)1019
WO1020 steps146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)1
CRTTfirst chunk (pooled)97 (+2.1%)137 (-14%)176 (-12%)196 (-41%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)122 (-10%)140 (-23%)203 (-18%)493 (-10%)114 (-38%)10
size sweep (100/s, 160B-12KB)127 (-3%)140 (-34%)195 (-67%)7053 (+695%)109 (-49%)10
replay gateway-gpt-5.4-nano-2000t (1x)119 (-12%)130 (-27%)186 (-22%)908 (+120%)224 (-32%)3
replay eve-gpt-5.6-sol-2000t (1x)124 (-14%)134 (-28%)179 (-38%)397 (-42%)331 (-48%)2
replay eve-gpt-5.6-sol-2000t (2x)176 (+17%)166 (-34%)225 (-56%)431 (-54%)231 (-51%)3
ℹ️ 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
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
❌ Failed E2E Tests
▲ Vercel Production (8 failed)
python-node (8 failed):
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE | 🔍 observability
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04 | 🔍 observability
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH | 🔍 observability
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456 | 🔍 observability
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ | 🔍 observability
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD | 🔍 observability
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6 | 🔍 observability
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1 | 🔍 observability
🌐 Cross-language Conformance (9 failed)
python (9 failed):
  • deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M13767WFNN55ZPS08TTWYSE5
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1
⚠️ 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.
10 flaky tests
  • abortParallelWorkflow: abort cancels all parallel steps (nextjs-webpack)
  • addTenWorkflow (sveltekit)
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (example)
  • deploymentId: 'latest' is a no-op in non-Vercel worlds (sveltekit)
  • hookWithSleepFinalStepWorkflow - step only on final payload (nextjs-turbopack)
  • hookWorkflow (vite)
  • importMetaUrlWorkflow - import.meta.url is available in step bundles (nextjs-webpack)
  • negative startIndex (reads from end) (fastify)
  • resilient start: addTenWorkflow completes when run_created returns 500 (nextjs-webpack)
  • webhookWorkflow (nextjs-webpack)
🛠 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 (tanstack-start) · at 03:36:34Z · abandoned wrun_01M1370T9QXQY5DGPV7Z4MM7CP
  • cold-start-warmup · suite warmup (python) · at 03:37:00Z · abandoned wrun_41M136YSW40GKY4DAMXP7CRT1J · (+6 more)
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:17Z · abandoned wrun_41M1372EW50GP2RNA9ZW12DSYM
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHJ0GYNMQ8EVS4VP59M
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRH
  • run-pickup-stall · sleepingWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRG
  • run-pickup-stall · nullByteWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHY0GNNW85TFDYFH6GT
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:49Z · abandoned wrun_41M1373E6A0GJJ736KSC91PHV8
  • cold-start-warmup · suite warmup (python) · at 03:37:49Z · abandoned wrun_01M13709F0CFVSSEQJ675KSV3N · (+7 more)
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKFV76GYY90JWAWA3H9
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKMJ95Q6FMXD9S91BZG
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:38:04Z · abandoned wrun_01M1373YKE0BJMG4K9KG19CQX7
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKRHSVK59E9BRNVXXWE
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKPQN9NRWNT72VZEK34
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SV0GZC31F122EX6ZA3
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749RC0GPK46HWB57ZK200
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749VJ0GXV6SVWDJE8Z8H5
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SK0GV08Z70ZBF8ADQE
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:38:58Z · abandoned wrun_41M1374D540GRDSCRGRXRTA0VJ
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:39:04Z · abandoned wrun_01M1375S74279D328PFRY93Q2E
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7AC88CCJ5Y13RECB57
  • run-pickup-stall · sleepingWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7C45FBF9CDSBCCAF55
  • run-pickup-stall · nullByteWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7J24TG2XANEEE3438V
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7FD9PG9WVJZT46G7CB
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:04Z · abandoned wrun_01M1377KTQJY02FZSJCAAC8B4B
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:05Z · abandoned wrun_01M1377KV0R0Z2F0DH4JVMP0HS
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:05Z · abandoned wrun_01M1377KV2E6YE3WGEJJTA2ER5
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H61VC8V106V4YWDTXM3
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H6DX7Y9CPGV467FHRFT
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:48Z · abandoned wrun_41M13771MX0GS1A8AX87B70570
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:48Z · abandoned wrun_41M137751P0GQHEK8MZJP94DPC
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:41:04Z · abandoned wrun_01M1379EE7EG775GYHVRPWY4GB
E2E Test Summary
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production357087424320
✅ 💻 Local Development392205584480
✅ 📦 Local Production392205584480
✅ 🐘 Local Postgres392205584480
✅ 🪟 Windows32000320
❌ 🌐 Cross-language Conformance09132141
✅ vercel-http-transport8170143960
✅ vercel-multi-region270027
✅ vercel-ws-transport553087640
Total1705317277819848
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro-node132028
✅ astro-quickjs132028
✅ example-node132028
✅ example-quickjs132028
✅ express-node132028
✅ express-quickjs132028
✅ fastify-node132028
✅ fastify-quickjs132028
✅ hono-node132028
✅ hono-quickjs132028
✅ nest-node132028
✅ nest-quickjs132028
✅ nextjs-turbopack-node15703
✅ nextjs-turbopack-quickjs15703
✅ nextjs-webpack-node15703
✅ nextjs-webpack-quickjs15703
✅ nitro-node132028
✅ nitro-quickjs132028
✅ nuxt-node132028
✅ nuxt-quickjs132028
❌ python-node08152
✅ sveltekit-node15109
✅ sveltekit-quickjs15109
✅ tanstack-start-node132028
✅ tanstack-start-quickjs132028
✅ vite-node132028
✅ vite-quickjs132028
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack-node16000
✅ nextjs-turbopack-quickjs16000
❌ 🌐 Cross-language Conformance
AppPassedFailedSkipped
❌ python09132
✅ vercel-http-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ hono132028
✅ nextjs-turbopack15703
✅ nitro132028
✅ vite132028
✅ vercel-multi-region
AppPassedFailedSkipped
✅ nextjs-turbopack2700
✅ vercel-ws-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ nextjs-turbopack15703
✅ vite132028
📋 View full workflow run
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Sim World
Simulated world deterministic testing for races. Traces
🟠 world-sim scenario book — 1 fail of 41 total
fence=per-spec
scenariooutcomeeventsvirtreplayviolations
✅ smoke-no-stepscompleted30msok0
✅ smoke-one-stepcompleted60msok0
✅ hook-at-step-startedcompleted120msok0
✅ hook-at-step-completedcompleted120msok0
✅ hook-at-hook-createdcompleted120msok0
✅ deadline-hook-winscompleted71.0hok0
✅ deadline-expirescompleted71.0hok0
✅ long-sleepcompleted1130.0dok0
✅ hook-never-arrivesstalled30msskipped0
✅ step-retries-twicecompleted102.0sok0
✅ parallel-stepscompleted90msok0
✅ hook-on-execution-statecompleted120msok0
✅ peek-hook-before-branchcompleted120msok0
✅ peek-hook-after-branchcompleted120msok0
✅ peek-hook-at-registrationcompleted120msok0
✅ race-hook-before-probecompleted120msok0
✅ race-hook-after-probecompleted120msok0
✅ race-duplicate-deliverycompleted130msok0
✅ attr-hook-before-stepcompleted110msok0
✅ attr-hook-after-stepcompleted110msok0
✅ attr-from-step-bodycompleted130msok0
✅ fork-hook-after-timeoutcompleted141.0mok0
✅ fork-hook-before-timeoutcompleted141.0mok0
✅ count-hook-after-timeoutcompleted171.0mok0
✅ count-hook-before-timeoutcompleted201.0mok0
✅ stale-read-step-count-forkcompleted201.0mok0
✅ stale-read-equal-step-countscompleted141.0mok0
✅ step-vs-step-forkcompleted120msok0
✅ step-vs-step-fork-fencedcompleted120msok0
✅ fence-catches-benign-directioncompleted125msok0
✅ in-flight-before-decisioncompleted171.0mok0
❌ in-flight-before-decision-countedcompleted171.0mok0
✅ in-flight-after-decisioncompleted192.0mok0
✅ stale-read-step-count-fork-fencedcompleted201.0mok0
✅ fork-hook-winscompleted131.0mok0
✅ fork-timeout-winscompleted131.0mok0
✅ unclaimed-payload-under-forkcompleted171.0mok0
✅ claimed-payload-under-forkcompleted171.0mok0
✅ writers-independent-step-bodiescompleted120msok0
✅ writers-scripted-tempocompleted120msok0
✅ cancel-mid-stepcancelled70msskipped0
Full trace: world-sim.txt
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
FrameworkFlow routeStep reg.Framework output
hono200.9 KiB (±0)40.3 KiB (+27 B)1.76 MiB (+753 B)
nextjs-turbopack206.3 KiB (±0)439 B (±0)763.7 KiB (+206 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.
1d5f28b · run
shalabhc
shalabhc
approved these changes
Aug 28, 2026
View reviewed changes
@shalabhcshalabhc
left a comment


Copy link


Copy Markdown

Collaborator
Choose a reason for hiding this comment

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

changeset looks too large tho
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment thread.changeset/quiet-normal-execution-logs.md
Outdated

'@workflow/world': patch
---

Stop logging on healthy workflow execution. A successful run now prints nothing;
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

make this more terse (see the other changlogs. should just be one-two line. not a story)
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

Trimmed to two sentences in 1d5f28b — matches the AGENTS.md guidance (one sentence, two at most) and the length of the other changelogs. The per-log-site rationale stays in the PR description. Package list and bump types are unchanged.
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment threadpackages/world-local/src/queue.ts
 // Debug-gated: this is the semaphore doing its job. A fan-out wider
 // than the limit queues behind it and every message still runs, so a
 // per-message warning turns a healthy wide run into a wall of output.
 debugLog(
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

nice fix!
@vercel@pranaygp
Trim the changeset to two sentences
1d5f28b
Review feedback: the changeset read as a story. AGENTS.md asks for one
sentence, or two at most; the per-log-site rationale already lives in the
PR description. Package list and bump types are unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
merged commit ffc5807
into
mainAug 28, 2026

181 of 183 checks passed

@pranaygp
pranaygp
deleted the

quiet-workflow-logs

branch
August 28, 2026 03:45
@github-actions
github-actionsBot
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
No backport to stable for ffc5807 (AI decision).
This is log-noise cleanup, not a stability fix: it changes existing logging behavior (warn/log downgraded to a DEBUG-gated debug line) and adds new public API surface (debugLog / isWorkflowDebugEnabled exported from @workflow/utils), with no correctness, crash, or resource issue being fixed. Its stated motivation is also largely main-only — packages/world-vercel/src/ws-transport.ts and docs/content/worlds/ do not exist on origin/stable, so the WebSocket-default fallout that drove the change does not affect the maintenance line. The residual bits that do apply on stable (packages/utils/src/get-port.ts, packages/world-local/src/queue.ts, packages/world/src/recovery.ts) are cosmetic verbosity changes that stable users can live without.
To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:
ffc58078d0c3cd2786d69bab7e41614566a9ea4e


This was referenced Aug 28, 2026
 Open

 Open

 Open

 Open

 Open

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

Reviewers

@shalabhcshalabhcshalabhc approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@pranaygp@shalabhc

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Stop logging on healthy workflow execution by pranaygp · Pull Request #3878 · vercel/workflow · GitHub
Skip to content
Stop logging on healthy workflow execution - #3878
Merged
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Aug 28, 2026
Merged
Stop logging on healthy workflow execution#3878
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Conversation
@pranaygp
@pranaygppranaygp
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
What
Normal workflow execution should print nothing. Today a healthy run emits several lines that only describe the runtime working correctly.
Most of it is fallout from #3702, which defaulted the events transport to WebSockets. Three log sites written while the transport was opt-in became default-path output, because each one reports a choice the caller no longer makes:
LineWhy it was fine when WS was opt-inWhy it is noise now
world-vercel: using ws events transport (…)Confirmed the flag took effectRuns once per cold start on every deployment, naming the transport it was always going to use
…requested but a World with projectConfig … falling backA real mismatch: someone asked for WS and didn't get itNobody asks now, so every CLI command and the observability app — all projectConfig Worlds — warn about a fallback they neither chose nor can act on
…received a drain notice (reason: max_duration…)Rare while few sockets existedmax_duration and auth_expiry are routine; the transport reconnects from the close that follows and no write is lost
Swept for the same shape elsewhere and found three more:
  • world-local queue concurrency — warned per message once a fan-out exceeded the limit. That is the semaphore doing its job; every message still runs.
  • @workflow/world active-run recovery — printed on every dev-server restart with work in flight. Resuming active runs is what a restart is for.
  • @workflow/utils port detection — two diagnostics gated on NODE_ENV=development, which is the only environment that reaches this code, so the gate made them unconditional for their entire audience. The getWorkflowPort one fires on an ordinary startup race (dev server still compiling its workflow routes) that the fallback then resolves correctly.
How
A new debugLog in @workflow/utils gates on DEBUG=workflow:* (or *), the same selector @workflow/core's logger already uses, so these join world-vercel's existing httpLog and logRetry output under one switch. It reads DEBUG per call rather than at module load, since Worlds are built long after import. @workflow/world hand-rolls the same check — that package deliberately carries no workspace dependencies, matching how env-config.ts hand-rolls globalSingleton().
Nothing about error logging changed. Every console.error / console.warn on a genuine fault is untouched, including the ws-transport's "failures are never silent" set and the re-enqueue failure sitting directly above the recovery line that did get gated — that one leaves a run unresumed. logger.warn / logger.error in @workflow/core still print unconditionally.
Testing
  • packages/{utils,world,world-local,world-vercel}/src — 1449 passed, 4 skipped.
  • packages/core/src — 2268 passed (unchanged; core consumes @workflow/utils).
  • New coverage: debug-log.test.ts (off by default, accepts workflow:* / *, ignores another library's selector, re-reads per call); ws-transport tests split into DEBUG / no-DEBUG pairs; recovery tests assert a successful recovery logs at no level while a failed re-enqueue still warns without DEBUG.
  • Verified the new ws-transport assertions bite: reverting ws-transport.ts alone fails exactly 4 of them.
  • biome check on the changed files reports the same 7 pre-existing warnings as base (exit 0); turbo typecheck clean for all four packages.
Two packages/utils/src/check-data-dir.test.ts cases fail on this machine on unmodified main as well — a leftover gitignored .workflow-data at the repo root that the test walks up and finds. Unrelated to this change.
Docs
worlds/v5/vercel.mdx claimed the projectConfig fallback logs a warning once per process. Updated to say it is silent and reported under DEBUG, and to point at workflow.events.transport on the per-write span as the durable answer to which transport carried a run.
🤖 Generated with Claude Code
@vercel@pranaygp
Stop logging on healthy workflow execution
64343e9
A successful run printed several lines that described the runtime working
correctly. Most of it was fallout from defaulting the events transport to
WebSockets (#3702): three breadcrumbs written while the transport was opt-in
became default-path output, because each one reported a choice the caller no
longer makes.
- `world-vercel: using ws events transport (…)` ran once per cold start on
every deployment, naming the transport it was always going to use.
- The `projectConfig` proxy fallback warned once per process. That World cannot
hold a socket, so with WS on by default every CLI command and the
observability app warned about a fallback nobody asked for and nobody can act
on. Debug-gated and reworded from "requested but" to "unavailable for".
- The `max_duration` / `auth_expiry` drain notice is routine: the transport
reconnects from the close that follows and no write is lost.
Swept for the same shape elsewhere:
- `world-local`'s queue-concurrency notice fired per message once a fan-out
exceeded the limit — the semaphore doing its job.
- `@workflow/world`'s active-run recovery line printed on every dev-server
restart with work in flight. The re-enqueue *failure* above it stays
unconditional; that one leaves a run unresumed.
- The port-detection diagnostics in `@workflow/utils` keyed off
`NODE_ENV=development`, which is the only environment that reaches them, so
the gate made them unconditional for their whole audience.
All of it moves behind `DEBUG=workflow:*` via a new `debugLog` in
`@workflow/utils`, joining world-vercel's existing `httpLog` and `logRetry`
output under one selector. Warnings and errors are untouched, so a run that
actually goes wrong is no quieter than before — the ws-transport tests that
assert failures are never silent still pass unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
requested a review
from a team
as a code ownerAugust 28, 2026 01:22
@changeset-bot
changeset-botBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 1d5f28b
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 23 packages
NameType
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/utilsPatch
@workflow/worldPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/vitestPatch
@workflow/world-postgresPatch
@workflow/aiPatch
@workflow/buildersPatch
@workflow/errorsPatch
@workflow/nestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/astroPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
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
vercelBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-nextjs-workflow-webpackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-astro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-express-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-fastify-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-hono-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nestjs-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nitro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nuxt-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-python-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-sveltekit-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-tanstack-start-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-vite-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-docsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-swc-playgroundReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-tarballsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-webReadyReadyPreview, v0Aug 28, 2026 3:36am
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
📊 Workflow Benchmarks
commit 1d5f28b · Fri, 28 Aug 2026 03:59:15 GMT · run logs
Backend: vercel · app: nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep658 (+250%) 🔻1372 🔴 (+23%) 🔻1411 🔴 (+23%) 🔻1544 🔴 (+6.0%)30
TTFSstream934 (+480%) 🔻1455 🔴 (+29%) 🔻1525 🔴 (+32%) 🔻1626 🔴 (+20%) 🔻30
TTFShook + stream1720 (+44%) 🔻1812 🔴 (+31%) 🔻1844 🔴 (+27%) 🔻1982 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)714 (+9.8%)2184 (+24%) 🔻2215 (+15%) 🔻2950 (+40%) 🔻10
Fan-out TTLSPromise.all(100 steps)2155 (+15%) 🔻4016 (+8.0%)4073 (+6.9%)10458 (+51%) 🔻10
STSO1020 steps (inline)133 (+22%) 🔻153 (-3.8%)172 (-7.0%)235 (-18%) 💚1019
WO1020 steps155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)1
CRTTfirst chunk (pooled)113 (+19%) 🔻146 (-8.2%)200 (+0.5%)238 (-29%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)139 (+2%)164 (-10%)265 (+7%)522 (-4%)144 (-22%)10
size sweep (100/s, 160B-12KB)137 (+5%)187 (-12%)263 (-55%)405 (-54%)119 (-44%)10
replay gateway-gpt-5.4-nano-2000t (1x)133 (-2%)149 (-16%)182 (-24%)890 (+115%)377 (+15%)3
replay eve-gpt-5.6-sol-2000t (1x)136 (-5%)155 (-16%)198 (-31%)370 (-46%)297 (-53%)2
replay eve-gpt-5.6-sol-2000t (2x)148 (-1%)214 (-15%)452 (-12%)1144 (+22%)344 (-28%)3
📈 STSO distribution vs main (inline / queue-hop histograms)
1020 steps (inline)
Cumulative STSO time: main 153650ms → this run 155201ms (Δ +1551ms, +1%)
100-150 ms ███████████████████████┃ main 681 this 687 +6
150-200 ms █████████░┃ main 264 this 302 +38
200-250 ms ┃█ main 52 this 23 -29
250-300 ms ┃ main 15 this 5 -10
300-350 ms ┃ main 5 this 0 -5
350-400 ms ┃ main 2 this 0 -2
400-450 ms ┃ main 0 this 2 +2

📈 CRTT drill-down vs main (RTT distributions & profiles)
variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▁▁··· 143 (-6%) 129 (-7%) 265 (+7%) 522 (-4%) 3000
sweep ······▂█▂···· 142 (-25%) 127 (-6%) 263 (-55%) 405 (-54%) 3000
gw 1x ·····▁▂█▁▁▁·· 140.4 (-6%) 127 (-5%) 182 (-24%) 890 (+115%) 5295
eve 1x ·····▁▃█▂▁··· 132.5 (-18%) 120 (-13%) 198 (-31%) 370 (-46%) 5186
eve 2x ·····▁▁█▃▁▁·· 179.4 (-19%) 150 (-14%) 452 (-12%) 1144 (+22%) 7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):
control ██▃▃▃▁█▅▂▂ 126–164ms
sweep █▅▅▃▃▂▁▂▃▂ 120–185ms
gw 1x ▂▁▁▁▁▃▂▁▁█ 123–233ms
eve 1x ▇▅▄▄▁▄▅█▆▇ 111–148ms
eve 2x ▁▁▁▂▁▂▃█▇▂ 140–295ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):
sweep ▁▁▃█▆▅▃ 140–145ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):
control ▁▅▅▄▃▆█▄▇▆ 39–49ms
sweep ▁▃█▅▇▅▄▆▄▅ 43–67ms
gw 1x ▂▂▂▁▂▅▆▃▂█ 37–56ms
eve 1x █▇▃▃▁▅▄▆▃▇ 21–29ms
eve 2x ▃█▁▄▅▃▂▅▄▆ 23–31ms

📜 Previous results (1)
64343e9
Fri, 28 Aug 2026 01:46:43 GMT · run logs
vercel / nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep183 (-2.7%)1314 🔴 (+18%) 🔻1383 🔴 (+20%) 🔻1480 🔴 (+1.6%)30
TTFSstream168 (+4.3%)1297 🔴 (+15%)1338 🔴 (+16%) 🔻1442 🔴 (+6.3%)30
TTFShook + stream1471 (+23%) 🔻1588 🔴 (+14%)1742 🔴 (+20%) 🔻1983 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)719 (+11%)2304 (+31%) 🔻2698 (+40%) 🔻2780 (+32%) 🔻10
Fan-out TTLSPromise.all(100 steps)1944 (+4.2%)4184 (+13%)4225 (+11%)9030 (+30%) 🔻10
STSO1020 steps (inline)101 (-7.3%)149 (-6.3%)179 (-3.2%)299 (+4.5%)1019
WO1020 steps146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)1
CRTTfirst chunk (pooled)97 (+2.1%)137 (-14%)176 (-12%)196 (-41%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)122 (-10%)140 (-23%)203 (-18%)493 (-10%)114 (-38%)10
size sweep (100/s, 160B-12KB)127 (-3%)140 (-34%)195 (-67%)7053 (+695%)109 (-49%)10
replay gateway-gpt-5.4-nano-2000t (1x)119 (-12%)130 (-27%)186 (-22%)908 (+120%)224 (-32%)3
replay eve-gpt-5.6-sol-2000t (1x)124 (-14%)134 (-28%)179 (-38%)397 (-42%)331 (-48%)2
replay eve-gpt-5.6-sol-2000t (2x)176 (+17%)166 (-34%)225 (-56%)431 (-54%)231 (-51%)3
ℹ️ 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
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
❌ Failed E2E Tests
▲ Vercel Production (8 failed)
python-node (8 failed):
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE | 🔍 observability
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04 | 🔍 observability
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH | 🔍 observability
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456 | 🔍 observability
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ | 🔍 observability
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD | 🔍 observability
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6 | 🔍 observability
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1 | 🔍 observability
🌐 Cross-language Conformance (9 failed)
python (9 failed):
  • deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M13767WFNN55ZPS08TTWYSE5
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1
⚠️ 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.
10 flaky tests
  • abortParallelWorkflow: abort cancels all parallel steps (nextjs-webpack)
  • addTenWorkflow (sveltekit)
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (example)
  • deploymentId: 'latest' is a no-op in non-Vercel worlds (sveltekit)
  • hookWithSleepFinalStepWorkflow - step only on final payload (nextjs-turbopack)
  • hookWorkflow (vite)
  • importMetaUrlWorkflow - import.meta.url is available in step bundles (nextjs-webpack)
  • negative startIndex (reads from end) (fastify)
  • resilient start: addTenWorkflow completes when run_created returns 500 (nextjs-webpack)
  • webhookWorkflow (nextjs-webpack)
🛠 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 (tanstack-start) · at 03:36:34Z · abandoned wrun_01M1370T9QXQY5DGPV7Z4MM7CP
  • cold-start-warmup · suite warmup (python) · at 03:37:00Z · abandoned wrun_41M136YSW40GKY4DAMXP7CRT1J · (+6 more)
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:17Z · abandoned wrun_41M1372EW50GP2RNA9ZW12DSYM
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHJ0GYNMQ8EVS4VP59M
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRH
  • run-pickup-stall · sleepingWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRG
  • run-pickup-stall · nullByteWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHY0GNNW85TFDYFH6GT
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:49Z · abandoned wrun_41M1373E6A0GJJ736KSC91PHV8
  • cold-start-warmup · suite warmup (python) · at 03:37:49Z · abandoned wrun_01M13709F0CFVSSEQJ675KSV3N · (+7 more)
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKFV76GYY90JWAWA3H9
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKMJ95Q6FMXD9S91BZG
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:38:04Z · abandoned wrun_01M1373YKE0BJMG4K9KG19CQX7
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKRHSVK59E9BRNVXXWE
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKPQN9NRWNT72VZEK34
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SV0GZC31F122EX6ZA3
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749RC0GPK46HWB57ZK200
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749VJ0GXV6SVWDJE8Z8H5
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SK0GV08Z70ZBF8ADQE
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:38:58Z · abandoned wrun_41M1374D540GRDSCRGRXRTA0VJ
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:39:04Z · abandoned wrun_01M1375S74279D328PFRY93Q2E
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7AC88CCJ5Y13RECB57
  • run-pickup-stall · sleepingWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7C45FBF9CDSBCCAF55
  • run-pickup-stall · nullByteWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7J24TG2XANEEE3438V
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7FD9PG9WVJZT46G7CB
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:04Z · abandoned wrun_01M1377KTQJY02FZSJCAAC8B4B
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:05Z · abandoned wrun_01M1377KV0R0Z2F0DH4JVMP0HS
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:05Z · abandoned wrun_01M1377KV2E6YE3WGEJJTA2ER5
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H61VC8V106V4YWDTXM3
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H6DX7Y9CPGV467FHRFT
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:48Z · abandoned wrun_41M13771MX0GS1A8AX87B70570
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:48Z · abandoned wrun_41M137751P0GQHEK8MZJP94DPC
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:41:04Z · abandoned wrun_01M1379EE7EG775GYHVRPWY4GB
E2E Test Summary
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production357087424320
✅ 💻 Local Development392205584480
✅ 📦 Local Production392205584480
✅ 🐘 Local Postgres392205584480
✅ 🪟 Windows32000320
❌ 🌐 Cross-language Conformance09132141
✅ vercel-http-transport8170143960
✅ vercel-multi-region270027
✅ vercel-ws-transport553087640
Total1705317277819848
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro-node132028
✅ astro-quickjs132028
✅ example-node132028
✅ example-quickjs132028
✅ express-node132028
✅ express-quickjs132028
✅ fastify-node132028
✅ fastify-quickjs132028
✅ hono-node132028
✅ hono-quickjs132028
✅ nest-node132028
✅ nest-quickjs132028
✅ nextjs-turbopack-node15703
✅ nextjs-turbopack-quickjs15703
✅ nextjs-webpack-node15703
✅ nextjs-webpack-quickjs15703
✅ nitro-node132028
✅ nitro-quickjs132028
✅ nuxt-node132028
✅ nuxt-quickjs132028
❌ python-node08152
✅ sveltekit-node15109
✅ sveltekit-quickjs15109
✅ tanstack-start-node132028
✅ tanstack-start-quickjs132028
✅ vite-node132028
✅ vite-quickjs132028
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack-node16000
✅ nextjs-turbopack-quickjs16000
❌ 🌐 Cross-language Conformance
AppPassedFailedSkipped
❌ python09132
✅ vercel-http-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ hono132028
✅ nextjs-turbopack15703
✅ nitro132028
✅ vite132028
✅ vercel-multi-region
AppPassedFailedSkipped
✅ nextjs-turbopack2700
✅ vercel-ws-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ nextjs-turbopack15703
✅ vite132028
📋 View full workflow run
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Sim World
Simulated world deterministic testing for races. Traces
🟠 world-sim scenario book — 1 fail of 41 total
fence=per-spec
scenariooutcomeeventsvirtreplayviolations
✅ smoke-no-stepscompleted30msok0
✅ smoke-one-stepcompleted60msok0
✅ hook-at-step-startedcompleted120msok0
✅ hook-at-step-completedcompleted120msok0
✅ hook-at-hook-createdcompleted120msok0
✅ deadline-hook-winscompleted71.0hok0
✅ deadline-expirescompleted71.0hok0
✅ long-sleepcompleted1130.0dok0
✅ hook-never-arrivesstalled30msskipped0
✅ step-retries-twicecompleted102.0sok0
✅ parallel-stepscompleted90msok0
✅ hook-on-execution-statecompleted120msok0
✅ peek-hook-before-branchcompleted120msok0
✅ peek-hook-after-branchcompleted120msok0
✅ peek-hook-at-registrationcompleted120msok0
✅ race-hook-before-probecompleted120msok0
✅ race-hook-after-probecompleted120msok0
✅ race-duplicate-deliverycompleted130msok0
✅ attr-hook-before-stepcompleted110msok0
✅ attr-hook-after-stepcompleted110msok0
✅ attr-from-step-bodycompleted130msok0
✅ fork-hook-after-timeoutcompleted141.0mok0
✅ fork-hook-before-timeoutcompleted141.0mok0
✅ count-hook-after-timeoutcompleted171.0mok0
✅ count-hook-before-timeoutcompleted201.0mok0
✅ stale-read-step-count-forkcompleted201.0mok0
✅ stale-read-equal-step-countscompleted141.0mok0
✅ step-vs-step-forkcompleted120msok0
✅ step-vs-step-fork-fencedcompleted120msok0
✅ fence-catches-benign-directioncompleted125msok0
✅ in-flight-before-decisioncompleted171.0mok0
❌ in-flight-before-decision-countedcompleted171.0mok0
✅ in-flight-after-decisioncompleted192.0mok0
✅ stale-read-step-count-fork-fencedcompleted201.0mok0
✅ fork-hook-winscompleted131.0mok0
✅ fork-timeout-winscompleted131.0mok0
✅ unclaimed-payload-under-forkcompleted171.0mok0
✅ claimed-payload-under-forkcompleted171.0mok0
✅ writers-independent-step-bodiescompleted120msok0
✅ writers-scripted-tempocompleted120msok0
✅ cancel-mid-stepcancelled70msskipped0
Full trace: world-sim.txt
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
FrameworkFlow routeStep reg.Framework output
hono200.9 KiB (±0)40.3 KiB (+27 B)1.76 MiB (+753 B)
nextjs-turbopack206.3 KiB (±0)439 B (±0)763.7 KiB (+206 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.
1d5f28b · run
shalabhc
shalabhc
approved these changes
Aug 28, 2026
View reviewed changes
@shalabhcshalabhc
left a comment


Copy link


Copy Markdown

Collaborator
Choose a reason for hiding this comment

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

changeset looks too large tho
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment thread.changeset/quiet-normal-execution-logs.md
Outdated

'@workflow/world': patch
---

Stop logging on healthy workflow execution. A successful run now prints nothing;
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

make this more terse (see the other changlogs. should just be one-two line. not a story)
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

Trimmed to two sentences in 1d5f28b — matches the AGENTS.md guidance (one sentence, two at most) and the length of the other changelogs. The per-log-site rationale stays in the PR description. Package list and bump types are unchanged.
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment threadpackages/world-local/src/queue.ts
 // Debug-gated: this is the semaphore doing its job. A fan-out wider
 // than the limit queues behind it and every message still runs, so a
 // per-message warning turns a healthy wide run into a wall of output.
 debugLog(
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

nice fix!
@vercel@pranaygp
Trim the changeset to two sentences
1d5f28b
Review feedback: the changeset read as a story. AGENTS.md asks for one
sentence, or two at most; the per-log-site rationale already lives in the
PR description. Package list and bump types are unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
merged commit ffc5807
into
mainAug 28, 2026

181 of 183 checks passed

@pranaygp
pranaygp
deleted the

quiet-workflow-logs

branch
August 28, 2026 03:45
@github-actions
github-actionsBot
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
No backport to stable for ffc5807 (AI decision).
This is log-noise cleanup, not a stability fix: it changes existing logging behavior (warn/log downgraded to a DEBUG-gated debug line) and adds new public API surface (debugLog / isWorkflowDebugEnabled exported from @workflow/utils), with no correctness, crash, or resource issue being fixed. Its stated motivation is also largely main-only — packages/world-vercel/src/ws-transport.ts and docs/content/worlds/ do not exist on origin/stable, so the WebSocket-default fallout that drove the change does not affect the maintenance line. The residual bits that do apply on stable (packages/utils/src/get-port.ts, packages/world-local/src/queue.ts, packages/world/src/recovery.ts) are cosmetic verbosity changes that stable users can live without.
To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:
ffc58078d0c3cd2786d69bab7e41614566a9ea4e


This was referenced Aug 28, 2026
 Open

 Open

 Open

 Open

 Open

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

Reviewers

@shalabhcshalabhcshalabhc approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@pranaygp@shalabhc

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Stop logging on healthy workflow execution by pranaygp · Pull Request #3878 · vercel/workflow · GitHub
Skip to content
Stop logging on healthy workflow execution - #3878
Merged
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Aug 28, 2026
Merged
Stop logging on healthy workflow execution#3878
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Conversation
@pranaygp
@pranaygppranaygp
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
What
Normal workflow execution should print nothing. Today a healthy run emits several lines that only describe the runtime working correctly.
Most of it is fallout from #3702, which defaulted the events transport to WebSockets. Three log sites written while the transport was opt-in became default-path output, because each one reports a choice the caller no longer makes:
LineWhy it was fine when WS was opt-inWhy it is noise now
world-vercel: using ws events transport (…)Confirmed the flag took effectRuns once per cold start on every deployment, naming the transport it was always going to use
…requested but a World with projectConfig … falling backA real mismatch: someone asked for WS and didn't get itNobody asks now, so every CLI command and the observability app — all projectConfig Worlds — warn about a fallback they neither chose nor can act on
…received a drain notice (reason: max_duration…)Rare while few sockets existedmax_duration and auth_expiry are routine; the transport reconnects from the close that follows and no write is lost
Swept for the same shape elsewhere and found three more:
  • world-local queue concurrency — warned per message once a fan-out exceeded the limit. That is the semaphore doing its job; every message still runs.
  • @workflow/world active-run recovery — printed on every dev-server restart with work in flight. Resuming active runs is what a restart is for.
  • @workflow/utils port detection — two diagnostics gated on NODE_ENV=development, which is the only environment that reaches this code, so the gate made them unconditional for their entire audience. The getWorkflowPort one fires on an ordinary startup race (dev server still compiling its workflow routes) that the fallback then resolves correctly.
How
A new debugLog in @workflow/utils gates on DEBUG=workflow:* (or *), the same selector @workflow/core's logger already uses, so these join world-vercel's existing httpLog and logRetry output under one switch. It reads DEBUG per call rather than at module load, since Worlds are built long after import. @workflow/world hand-rolls the same check — that package deliberately carries no workspace dependencies, matching how env-config.ts hand-rolls globalSingleton().
Nothing about error logging changed. Every console.error / console.warn on a genuine fault is untouched, including the ws-transport's "failures are never silent" set and the re-enqueue failure sitting directly above the recovery line that did get gated — that one leaves a run unresumed. logger.warn / logger.error in @workflow/core still print unconditionally.
Testing
  • packages/{utils,world,world-local,world-vercel}/src — 1449 passed, 4 skipped.
  • packages/core/src — 2268 passed (unchanged; core consumes @workflow/utils).
  • New coverage: debug-log.test.ts (off by default, accepts workflow:* / *, ignores another library's selector, re-reads per call); ws-transport tests split into DEBUG / no-DEBUG pairs; recovery tests assert a successful recovery logs at no level while a failed re-enqueue still warns without DEBUG.
  • Verified the new ws-transport assertions bite: reverting ws-transport.ts alone fails exactly 4 of them.
  • biome check on the changed files reports the same 7 pre-existing warnings as base (exit 0); turbo typecheck clean for all four packages.
Two packages/utils/src/check-data-dir.test.ts cases fail on this machine on unmodified main as well — a leftover gitignored .workflow-data at the repo root that the test walks up and finds. Unrelated to this change.
Docs
worlds/v5/vercel.mdx claimed the projectConfig fallback logs a warning once per process. Updated to say it is silent and reported under DEBUG, and to point at workflow.events.transport on the per-write span as the durable answer to which transport carried a run.
🤖 Generated with Claude Code
@vercel@pranaygp
Stop logging on healthy workflow execution
64343e9
A successful run printed several lines that described the runtime working
correctly. Most of it was fallout from defaulting the events transport to
WebSockets (#3702): three breadcrumbs written while the transport was opt-in
became default-path output, because each one reported a choice the caller no
longer makes.
- `world-vercel: using ws events transport (…)` ran once per cold start on
every deployment, naming the transport it was always going to use.
- The `projectConfig` proxy fallback warned once per process. That World cannot
hold a socket, so with WS on by default every CLI command and the
observability app warned about a fallback nobody asked for and nobody can act
on. Debug-gated and reworded from "requested but" to "unavailable for".
- The `max_duration` / `auth_expiry` drain notice is routine: the transport
reconnects from the close that follows and no write is lost.
Swept for the same shape elsewhere:
- `world-local`'s queue-concurrency notice fired per message once a fan-out
exceeded the limit — the semaphore doing its job.
- `@workflow/world`'s active-run recovery line printed on every dev-server
restart with work in flight. The re-enqueue *failure* above it stays
unconditional; that one leaves a run unresumed.
- The port-detection diagnostics in `@workflow/utils` keyed off
`NODE_ENV=development`, which is the only environment that reaches them, so
the gate made them unconditional for their whole audience.
All of it moves behind `DEBUG=workflow:*` via a new `debugLog` in
`@workflow/utils`, joining world-vercel's existing `httpLog` and `logRetry`
output under one selector. Warnings and errors are untouched, so a run that
actually goes wrong is no quieter than before — the ws-transport tests that
assert failures are never silent still pass unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
requested a review
from a team
as a code ownerAugust 28, 2026 01:22
@changeset-bot
changeset-botBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 1d5f28b
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 23 packages
NameType
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/utilsPatch
@workflow/worldPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/vitestPatch
@workflow/world-postgresPatch
@workflow/aiPatch
@workflow/buildersPatch
@workflow/errorsPatch
@workflow/nestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/astroPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
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
vercelBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-nextjs-workflow-webpackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-astro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-express-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-fastify-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-hono-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nestjs-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nitro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nuxt-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-python-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-sveltekit-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-tanstack-start-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-vite-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-docsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-swc-playgroundReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-tarballsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-webReadyReadyPreview, v0Aug 28, 2026 3:36am
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
📊 Workflow Benchmarks
commit 1d5f28b · Fri, 28 Aug 2026 03:59:15 GMT · run logs
Backend: vercel · app: nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep658 (+250%) 🔻1372 🔴 (+23%) 🔻1411 🔴 (+23%) 🔻1544 🔴 (+6.0%)30
TTFSstream934 (+480%) 🔻1455 🔴 (+29%) 🔻1525 🔴 (+32%) 🔻1626 🔴 (+20%) 🔻30
TTFShook + stream1720 (+44%) 🔻1812 🔴 (+31%) 🔻1844 🔴 (+27%) 🔻1982 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)714 (+9.8%)2184 (+24%) 🔻2215 (+15%) 🔻2950 (+40%) 🔻10
Fan-out TTLSPromise.all(100 steps)2155 (+15%) 🔻4016 (+8.0%)4073 (+6.9%)10458 (+51%) 🔻10
STSO1020 steps (inline)133 (+22%) 🔻153 (-3.8%)172 (-7.0%)235 (-18%) 💚1019
WO1020 steps155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)1
CRTTfirst chunk (pooled)113 (+19%) 🔻146 (-8.2%)200 (+0.5%)238 (-29%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)139 (+2%)164 (-10%)265 (+7%)522 (-4%)144 (-22%)10
size sweep (100/s, 160B-12KB)137 (+5%)187 (-12%)263 (-55%)405 (-54%)119 (-44%)10
replay gateway-gpt-5.4-nano-2000t (1x)133 (-2%)149 (-16%)182 (-24%)890 (+115%)377 (+15%)3
replay eve-gpt-5.6-sol-2000t (1x)136 (-5%)155 (-16%)198 (-31%)370 (-46%)297 (-53%)2
replay eve-gpt-5.6-sol-2000t (2x)148 (-1%)214 (-15%)452 (-12%)1144 (+22%)344 (-28%)3
📈 STSO distribution vs main (inline / queue-hop histograms)
1020 steps (inline)
Cumulative STSO time: main 153650ms → this run 155201ms (Δ +1551ms, +1%)
100-150 ms ███████████████████████┃ main 681 this 687 +6
150-200 ms █████████░┃ main 264 this 302 +38
200-250 ms ┃█ main 52 this 23 -29
250-300 ms ┃ main 15 this 5 -10
300-350 ms ┃ main 5 this 0 -5
350-400 ms ┃ main 2 this 0 -2
400-450 ms ┃ main 0 this 2 +2

📈 CRTT drill-down vs main (RTT distributions & profiles)
variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▁▁··· 143 (-6%) 129 (-7%) 265 (+7%) 522 (-4%) 3000
sweep ······▂█▂···· 142 (-25%) 127 (-6%) 263 (-55%) 405 (-54%) 3000
gw 1x ·····▁▂█▁▁▁·· 140.4 (-6%) 127 (-5%) 182 (-24%) 890 (+115%) 5295
eve 1x ·····▁▃█▂▁··· 132.5 (-18%) 120 (-13%) 198 (-31%) 370 (-46%) 5186
eve 2x ·····▁▁█▃▁▁·· 179.4 (-19%) 150 (-14%) 452 (-12%) 1144 (+22%) 7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):
control ██▃▃▃▁█▅▂▂ 126–164ms
sweep █▅▅▃▃▂▁▂▃▂ 120–185ms
gw 1x ▂▁▁▁▁▃▂▁▁█ 123–233ms
eve 1x ▇▅▄▄▁▄▅█▆▇ 111–148ms
eve 2x ▁▁▁▂▁▂▃█▇▂ 140–295ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):
sweep ▁▁▃█▆▅▃ 140–145ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):
control ▁▅▅▄▃▆█▄▇▆ 39–49ms
sweep ▁▃█▅▇▅▄▆▄▅ 43–67ms
gw 1x ▂▂▂▁▂▅▆▃▂█ 37–56ms
eve 1x █▇▃▃▁▅▄▆▃▇ 21–29ms
eve 2x ▃█▁▄▅▃▂▅▄▆ 23–31ms

📜 Previous results (1)
64343e9
Fri, 28 Aug 2026 01:46:43 GMT · run logs
vercel / nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep183 (-2.7%)1314 🔴 (+18%) 🔻1383 🔴 (+20%) 🔻1480 🔴 (+1.6%)30
TTFSstream168 (+4.3%)1297 🔴 (+15%)1338 🔴 (+16%) 🔻1442 🔴 (+6.3%)30
TTFShook + stream1471 (+23%) 🔻1588 🔴 (+14%)1742 🔴 (+20%) 🔻1983 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)719 (+11%)2304 (+31%) 🔻2698 (+40%) 🔻2780 (+32%) 🔻10
Fan-out TTLSPromise.all(100 steps)1944 (+4.2%)4184 (+13%)4225 (+11%)9030 (+30%) 🔻10
STSO1020 steps (inline)101 (-7.3%)149 (-6.3%)179 (-3.2%)299 (+4.5%)1019
WO1020 steps146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)1
CRTTfirst chunk (pooled)97 (+2.1%)137 (-14%)176 (-12%)196 (-41%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)122 (-10%)140 (-23%)203 (-18%)493 (-10%)114 (-38%)10
size sweep (100/s, 160B-12KB)127 (-3%)140 (-34%)195 (-67%)7053 (+695%)109 (-49%)10
replay gateway-gpt-5.4-nano-2000t (1x)119 (-12%)130 (-27%)186 (-22%)908 (+120%)224 (-32%)3
replay eve-gpt-5.6-sol-2000t (1x)124 (-14%)134 (-28%)179 (-38%)397 (-42%)331 (-48%)2
replay eve-gpt-5.6-sol-2000t (2x)176 (+17%)166 (-34%)225 (-56%)431 (-54%)231 (-51%)3
ℹ️ 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
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
❌ Failed E2E Tests
▲ Vercel Production (8 failed)
python-node (8 failed):
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE | 🔍 observability
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04 | 🔍 observability
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH | 🔍 observability
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456 | 🔍 observability
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ | 🔍 observability
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD | 🔍 observability
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6 | 🔍 observability
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1 | 🔍 observability
🌐 Cross-language Conformance (9 failed)
python (9 failed):
  • deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M13767WFNN55ZPS08TTWYSE5
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1
⚠️ 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.
10 flaky tests
  • abortParallelWorkflow: abort cancels all parallel steps (nextjs-webpack)
  • addTenWorkflow (sveltekit)
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (example)
  • deploymentId: 'latest' is a no-op in non-Vercel worlds (sveltekit)
  • hookWithSleepFinalStepWorkflow - step only on final payload (nextjs-turbopack)
  • hookWorkflow (vite)
  • importMetaUrlWorkflow - import.meta.url is available in step bundles (nextjs-webpack)
  • negative startIndex (reads from end) (fastify)
  • resilient start: addTenWorkflow completes when run_created returns 500 (nextjs-webpack)
  • webhookWorkflow (nextjs-webpack)
🛠 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 (tanstack-start) · at 03:36:34Z · abandoned wrun_01M1370T9QXQY5DGPV7Z4MM7CP
  • cold-start-warmup · suite warmup (python) · at 03:37:00Z · abandoned wrun_41M136YSW40GKY4DAMXP7CRT1J · (+6 more)
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:17Z · abandoned wrun_41M1372EW50GP2RNA9ZW12DSYM
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHJ0GYNMQ8EVS4VP59M
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRH
  • run-pickup-stall · sleepingWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRG
  • run-pickup-stall · nullByteWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHY0GNNW85TFDYFH6GT
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:49Z · abandoned wrun_41M1373E6A0GJJ736KSC91PHV8
  • cold-start-warmup · suite warmup (python) · at 03:37:49Z · abandoned wrun_01M13709F0CFVSSEQJ675KSV3N · (+7 more)
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKFV76GYY90JWAWA3H9
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKMJ95Q6FMXD9S91BZG
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:38:04Z · abandoned wrun_01M1373YKE0BJMG4K9KG19CQX7
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKRHSVK59E9BRNVXXWE
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKPQN9NRWNT72VZEK34
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SV0GZC31F122EX6ZA3
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749RC0GPK46HWB57ZK200
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749VJ0GXV6SVWDJE8Z8H5
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SK0GV08Z70ZBF8ADQE
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:38:58Z · abandoned wrun_41M1374D540GRDSCRGRXRTA0VJ
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:39:04Z · abandoned wrun_01M1375S74279D328PFRY93Q2E
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7AC88CCJ5Y13RECB57
  • run-pickup-stall · sleepingWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7C45FBF9CDSBCCAF55
  • run-pickup-stall · nullByteWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7J24TG2XANEEE3438V
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7FD9PG9WVJZT46G7CB
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:04Z · abandoned wrun_01M1377KTQJY02FZSJCAAC8B4B
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:05Z · abandoned wrun_01M1377KV0R0Z2F0DH4JVMP0HS
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:05Z · abandoned wrun_01M1377KV2E6YE3WGEJJTA2ER5
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H61VC8V106V4YWDTXM3
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H6DX7Y9CPGV467FHRFT
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:48Z · abandoned wrun_41M13771MX0GS1A8AX87B70570
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:48Z · abandoned wrun_41M137751P0GQHEK8MZJP94DPC
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:41:04Z · abandoned wrun_01M1379EE7EG775GYHVRPWY4GB
E2E Test Summary
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production357087424320
✅ 💻 Local Development392205584480
✅ 📦 Local Production392205584480
✅ 🐘 Local Postgres392205584480
✅ 🪟 Windows32000320
❌ 🌐 Cross-language Conformance09132141
✅ vercel-http-transport8170143960
✅ vercel-multi-region270027
✅ vercel-ws-transport553087640
Total1705317277819848
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro-node132028
✅ astro-quickjs132028
✅ example-node132028
✅ example-quickjs132028
✅ express-node132028
✅ express-quickjs132028
✅ fastify-node132028
✅ fastify-quickjs132028
✅ hono-node132028
✅ hono-quickjs132028
✅ nest-node132028
✅ nest-quickjs132028
✅ nextjs-turbopack-node15703
✅ nextjs-turbopack-quickjs15703
✅ nextjs-webpack-node15703
✅ nextjs-webpack-quickjs15703
✅ nitro-node132028
✅ nitro-quickjs132028
✅ nuxt-node132028
✅ nuxt-quickjs132028
❌ python-node08152
✅ sveltekit-node15109
✅ sveltekit-quickjs15109
✅ tanstack-start-node132028
✅ tanstack-start-quickjs132028
✅ vite-node132028
✅ vite-quickjs132028
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack-node16000
✅ nextjs-turbopack-quickjs16000
❌ 🌐 Cross-language Conformance
AppPassedFailedSkipped
❌ python09132
✅ vercel-http-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ hono132028
✅ nextjs-turbopack15703
✅ nitro132028
✅ vite132028
✅ vercel-multi-region
AppPassedFailedSkipped
✅ nextjs-turbopack2700
✅ vercel-ws-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ nextjs-turbopack15703
✅ vite132028
📋 View full workflow run
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Sim World
Simulated world deterministic testing for races. Traces
🟠 world-sim scenario book — 1 fail of 41 total
fence=per-spec
scenariooutcomeeventsvirtreplayviolations
✅ smoke-no-stepscompleted30msok0
✅ smoke-one-stepcompleted60msok0
✅ hook-at-step-startedcompleted120msok0
✅ hook-at-step-completedcompleted120msok0
✅ hook-at-hook-createdcompleted120msok0
✅ deadline-hook-winscompleted71.0hok0
✅ deadline-expirescompleted71.0hok0
✅ long-sleepcompleted1130.0dok0
✅ hook-never-arrivesstalled30msskipped0
✅ step-retries-twicecompleted102.0sok0
✅ parallel-stepscompleted90msok0
✅ hook-on-execution-statecompleted120msok0
✅ peek-hook-before-branchcompleted120msok0
✅ peek-hook-after-branchcompleted120msok0
✅ peek-hook-at-registrationcompleted120msok0
✅ race-hook-before-probecompleted120msok0
✅ race-hook-after-probecompleted120msok0
✅ race-duplicate-deliverycompleted130msok0
✅ attr-hook-before-stepcompleted110msok0
✅ attr-hook-after-stepcompleted110msok0
✅ attr-from-step-bodycompleted130msok0
✅ fork-hook-after-timeoutcompleted141.0mok0
✅ fork-hook-before-timeoutcompleted141.0mok0
✅ count-hook-after-timeoutcompleted171.0mok0
✅ count-hook-before-timeoutcompleted201.0mok0
✅ stale-read-step-count-forkcompleted201.0mok0
✅ stale-read-equal-step-countscompleted141.0mok0
✅ step-vs-step-forkcompleted120msok0
✅ step-vs-step-fork-fencedcompleted120msok0
✅ fence-catches-benign-directioncompleted125msok0
✅ in-flight-before-decisioncompleted171.0mok0
❌ in-flight-before-decision-countedcompleted171.0mok0
✅ in-flight-after-decisioncompleted192.0mok0
✅ stale-read-step-count-fork-fencedcompleted201.0mok0
✅ fork-hook-winscompleted131.0mok0
✅ fork-timeout-winscompleted131.0mok0
✅ unclaimed-payload-under-forkcompleted171.0mok0
✅ claimed-payload-under-forkcompleted171.0mok0
✅ writers-independent-step-bodiescompleted120msok0
✅ writers-scripted-tempocompleted120msok0
✅ cancel-mid-stepcancelled70msskipped0
Full trace: world-sim.txt
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
FrameworkFlow routeStep reg.Framework output
hono200.9 KiB (±0)40.3 KiB (+27 B)1.76 MiB (+753 B)
nextjs-turbopack206.3 KiB (±0)439 B (±0)763.7 KiB (+206 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.
1d5f28b · run
shalabhc
shalabhc
approved these changes
Aug 28, 2026
View reviewed changes
@shalabhcshalabhc
left a comment


Copy link


Copy Markdown

Collaborator
Choose a reason for hiding this comment

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

changeset looks too large tho
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment thread.changeset/quiet-normal-execution-logs.md
Outdated

'@workflow/world': patch
---

Stop logging on healthy workflow execution. A successful run now prints nothing;
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

make this more terse (see the other changlogs. should just be one-two line. not a story)
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

Trimmed to two sentences in 1d5f28b — matches the AGENTS.md guidance (one sentence, two at most) and the length of the other changelogs. The per-log-site rationale stays in the PR description. Package list and bump types are unchanged.
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment threadpackages/world-local/src/queue.ts
 // Debug-gated: this is the semaphore doing its job. A fan-out wider
 // than the limit queues behind it and every message still runs, so a
 // per-message warning turns a healthy wide run into a wall of output.
 debugLog(
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

nice fix!
@vercel@pranaygp
Trim the changeset to two sentences
1d5f28b
Review feedback: the changeset read as a story. AGENTS.md asks for one
sentence, or two at most; the per-log-site rationale already lives in the
PR description. Package list and bump types are unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
merged commit ffc5807
into
mainAug 28, 2026

181 of 183 checks passed

@pranaygp
pranaygp
deleted the

quiet-workflow-logs

branch
August 28, 2026 03:45
@github-actions
github-actionsBot
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
No backport to stable for ffc5807 (AI decision).
This is log-noise cleanup, not a stability fix: it changes existing logging behavior (warn/log downgraded to a DEBUG-gated debug line) and adds new public API surface (debugLog / isWorkflowDebugEnabled exported from @workflow/utils), with no correctness, crash, or resource issue being fixed. Its stated motivation is also largely main-only — packages/world-vercel/src/ws-transport.ts and docs/content/worlds/ do not exist on origin/stable, so the WebSocket-default fallout that drove the change does not affect the maintenance line. The residual bits that do apply on stable (packages/utils/src/get-port.ts, packages/world-local/src/queue.ts, packages/world/src/recovery.ts) are cosmetic verbosity changes that stable users can live without.
To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:
ffc58078d0c3cd2786d69bab7e41614566a9ea4e


This was referenced Aug 28, 2026
 Open

 Open

 Open

 Open

 Open

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

Reviewers

@shalabhcshalabhcshalabhc approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@pranaygp@shalabhc

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Stop logging on healthy workflow execution by pranaygp · Pull Request #3878 · vercel/workflow · GitHub
Skip to content
Stop logging on healthy workflow execution - #3878
Merged
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Aug 28, 2026
Merged
Stop logging on healthy workflow execution#3878
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Conversation
@pranaygp
@pranaygppranaygp
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
What
Normal workflow execution should print nothing. Today a healthy run emits several lines that only describe the runtime working correctly.
Most of it is fallout from #3702, which defaulted the events transport to WebSockets. Three log sites written while the transport was opt-in became default-path output, because each one reports a choice the caller no longer makes:
LineWhy it was fine when WS was opt-inWhy it is noise now
world-vercel: using ws events transport (…)Confirmed the flag took effectRuns once per cold start on every deployment, naming the transport it was always going to use
…requested but a World with projectConfig … falling backA real mismatch: someone asked for WS and didn't get itNobody asks now, so every CLI command and the observability app — all projectConfig Worlds — warn about a fallback they neither chose nor can act on
…received a drain notice (reason: max_duration…)Rare while few sockets existedmax_duration and auth_expiry are routine; the transport reconnects from the close that follows and no write is lost
Swept for the same shape elsewhere and found three more:
  • world-local queue concurrency — warned per message once a fan-out exceeded the limit. That is the semaphore doing its job; every message still runs.
  • @workflow/world active-run recovery — printed on every dev-server restart with work in flight. Resuming active runs is what a restart is for.
  • @workflow/utils port detection — two diagnostics gated on NODE_ENV=development, which is the only environment that reaches this code, so the gate made them unconditional for their entire audience. The getWorkflowPort one fires on an ordinary startup race (dev server still compiling its workflow routes) that the fallback then resolves correctly.
How
A new debugLog in @workflow/utils gates on DEBUG=workflow:* (or *), the same selector @workflow/core's logger already uses, so these join world-vercel's existing httpLog and logRetry output under one switch. It reads DEBUG per call rather than at module load, since Worlds are built long after import. @workflow/world hand-rolls the same check — that package deliberately carries no workspace dependencies, matching how env-config.ts hand-rolls globalSingleton().
Nothing about error logging changed. Every console.error / console.warn on a genuine fault is untouched, including the ws-transport's "failures are never silent" set and the re-enqueue failure sitting directly above the recovery line that did get gated — that one leaves a run unresumed. logger.warn / logger.error in @workflow/core still print unconditionally.
Testing
  • packages/{utils,world,world-local,world-vercel}/src — 1449 passed, 4 skipped.
  • packages/core/src — 2268 passed (unchanged; core consumes @workflow/utils).
  • New coverage: debug-log.test.ts (off by default, accepts workflow:* / *, ignores another library's selector, re-reads per call); ws-transport tests split into DEBUG / no-DEBUG pairs; recovery tests assert a successful recovery logs at no level while a failed re-enqueue still warns without DEBUG.
  • Verified the new ws-transport assertions bite: reverting ws-transport.ts alone fails exactly 4 of them.
  • biome check on the changed files reports the same 7 pre-existing warnings as base (exit 0); turbo typecheck clean for all four packages.
Two packages/utils/src/check-data-dir.test.ts cases fail on this machine on unmodified main as well — a leftover gitignored .workflow-data at the repo root that the test walks up and finds. Unrelated to this change.
Docs
worlds/v5/vercel.mdx claimed the projectConfig fallback logs a warning once per process. Updated to say it is silent and reported under DEBUG, and to point at workflow.events.transport on the per-write span as the durable answer to which transport carried a run.
🤖 Generated with Claude Code
@vercel@pranaygp
Stop logging on healthy workflow execution
64343e9
A successful run printed several lines that described the runtime working
correctly. Most of it was fallout from defaulting the events transport to
WebSockets (#3702): three breadcrumbs written while the transport was opt-in
became default-path output, because each one reported a choice the caller no
longer makes.
- `world-vercel: using ws events transport (…)` ran once per cold start on
every deployment, naming the transport it was always going to use.
- The `projectConfig` proxy fallback warned once per process. That World cannot
hold a socket, so with WS on by default every CLI command and the
observability app warned about a fallback nobody asked for and nobody can act
on. Debug-gated and reworded from "requested but" to "unavailable for".
- The `max_duration` / `auth_expiry` drain notice is routine: the transport
reconnects from the close that follows and no write is lost.
Swept for the same shape elsewhere:
- `world-local`'s queue-concurrency notice fired per message once a fan-out
exceeded the limit — the semaphore doing its job.
- `@workflow/world`'s active-run recovery line printed on every dev-server
restart with work in flight. The re-enqueue *failure* above it stays
unconditional; that one leaves a run unresumed.
- The port-detection diagnostics in `@workflow/utils` keyed off
`NODE_ENV=development`, which is the only environment that reaches them, so
the gate made them unconditional for their whole audience.
All of it moves behind `DEBUG=workflow:*` via a new `debugLog` in
`@workflow/utils`, joining world-vercel's existing `httpLog` and `logRetry`
output under one selector. Warnings and errors are untouched, so a run that
actually goes wrong is no quieter than before — the ws-transport tests that
assert failures are never silent still pass unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
requested a review
from a team
as a code ownerAugust 28, 2026 01:22
@changeset-bot
changeset-botBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 1d5f28b
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 23 packages
NameType
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/utilsPatch
@workflow/worldPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/vitestPatch
@workflow/world-postgresPatch
@workflow/aiPatch
@workflow/buildersPatch
@workflow/errorsPatch
@workflow/nestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/astroPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
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
vercelBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-nextjs-workflow-webpackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-astro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-express-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-fastify-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-hono-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nestjs-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nitro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nuxt-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-python-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-sveltekit-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-tanstack-start-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-vite-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-docsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-swc-playgroundReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-tarballsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-webReadyReadyPreview, v0Aug 28, 2026 3:36am
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
📊 Workflow Benchmarks
commit 1d5f28b · Fri, 28 Aug 2026 03:59:15 GMT · run logs
Backend: vercel · app: nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep658 (+250%) 🔻1372 🔴 (+23%) 🔻1411 🔴 (+23%) 🔻1544 🔴 (+6.0%)30
TTFSstream934 (+480%) 🔻1455 🔴 (+29%) 🔻1525 🔴 (+32%) 🔻1626 🔴 (+20%) 🔻30
TTFShook + stream1720 (+44%) 🔻1812 🔴 (+31%) 🔻1844 🔴 (+27%) 🔻1982 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)714 (+9.8%)2184 (+24%) 🔻2215 (+15%) 🔻2950 (+40%) 🔻10
Fan-out TTLSPromise.all(100 steps)2155 (+15%) 🔻4016 (+8.0%)4073 (+6.9%)10458 (+51%) 🔻10
STSO1020 steps (inline)133 (+22%) 🔻153 (-3.8%)172 (-7.0%)235 (-18%) 💚1019
WO1020 steps155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)1
CRTTfirst chunk (pooled)113 (+19%) 🔻146 (-8.2%)200 (+0.5%)238 (-29%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)139 (+2%)164 (-10%)265 (+7%)522 (-4%)144 (-22%)10
size sweep (100/s, 160B-12KB)137 (+5%)187 (-12%)263 (-55%)405 (-54%)119 (-44%)10
replay gateway-gpt-5.4-nano-2000t (1x)133 (-2%)149 (-16%)182 (-24%)890 (+115%)377 (+15%)3
replay eve-gpt-5.6-sol-2000t (1x)136 (-5%)155 (-16%)198 (-31%)370 (-46%)297 (-53%)2
replay eve-gpt-5.6-sol-2000t (2x)148 (-1%)214 (-15%)452 (-12%)1144 (+22%)344 (-28%)3
📈 STSO distribution vs main (inline / queue-hop histograms)
1020 steps (inline)
Cumulative STSO time: main 153650ms → this run 155201ms (Δ +1551ms, +1%)
100-150 ms ███████████████████████┃ main 681 this 687 +6
150-200 ms █████████░┃ main 264 this 302 +38
200-250 ms ┃█ main 52 this 23 -29
250-300 ms ┃ main 15 this 5 -10
300-350 ms ┃ main 5 this 0 -5
350-400 ms ┃ main 2 this 0 -2
400-450 ms ┃ main 0 this 2 +2

📈 CRTT drill-down vs main (RTT distributions & profiles)
variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▁▁··· 143 (-6%) 129 (-7%) 265 (+7%) 522 (-4%) 3000
sweep ······▂█▂···· 142 (-25%) 127 (-6%) 263 (-55%) 405 (-54%) 3000
gw 1x ·····▁▂█▁▁▁·· 140.4 (-6%) 127 (-5%) 182 (-24%) 890 (+115%) 5295
eve 1x ·····▁▃█▂▁··· 132.5 (-18%) 120 (-13%) 198 (-31%) 370 (-46%) 5186
eve 2x ·····▁▁█▃▁▁·· 179.4 (-19%) 150 (-14%) 452 (-12%) 1144 (+22%) 7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):
control ██▃▃▃▁█▅▂▂ 126–164ms
sweep █▅▅▃▃▂▁▂▃▂ 120–185ms
gw 1x ▂▁▁▁▁▃▂▁▁█ 123–233ms
eve 1x ▇▅▄▄▁▄▅█▆▇ 111–148ms
eve 2x ▁▁▁▂▁▂▃█▇▂ 140–295ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):
sweep ▁▁▃█▆▅▃ 140–145ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):
control ▁▅▅▄▃▆█▄▇▆ 39–49ms
sweep ▁▃█▅▇▅▄▆▄▅ 43–67ms
gw 1x ▂▂▂▁▂▅▆▃▂█ 37–56ms
eve 1x █▇▃▃▁▅▄▆▃▇ 21–29ms
eve 2x ▃█▁▄▅▃▂▅▄▆ 23–31ms

📜 Previous results (1)
64343e9
Fri, 28 Aug 2026 01:46:43 GMT · run logs
vercel / nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep183 (-2.7%)1314 🔴 (+18%) 🔻1383 🔴 (+20%) 🔻1480 🔴 (+1.6%)30
TTFSstream168 (+4.3%)1297 🔴 (+15%)1338 🔴 (+16%) 🔻1442 🔴 (+6.3%)30
TTFShook + stream1471 (+23%) 🔻1588 🔴 (+14%)1742 🔴 (+20%) 🔻1983 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)719 (+11%)2304 (+31%) 🔻2698 (+40%) 🔻2780 (+32%) 🔻10
Fan-out TTLSPromise.all(100 steps)1944 (+4.2%)4184 (+13%)4225 (+11%)9030 (+30%) 🔻10
STSO1020 steps (inline)101 (-7.3%)149 (-6.3%)179 (-3.2%)299 (+4.5%)1019
WO1020 steps146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)1
CRTTfirst chunk (pooled)97 (+2.1%)137 (-14%)176 (-12%)196 (-41%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)122 (-10%)140 (-23%)203 (-18%)493 (-10%)114 (-38%)10
size sweep (100/s, 160B-12KB)127 (-3%)140 (-34%)195 (-67%)7053 (+695%)109 (-49%)10
replay gateway-gpt-5.4-nano-2000t (1x)119 (-12%)130 (-27%)186 (-22%)908 (+120%)224 (-32%)3
replay eve-gpt-5.6-sol-2000t (1x)124 (-14%)134 (-28%)179 (-38%)397 (-42%)331 (-48%)2
replay eve-gpt-5.6-sol-2000t (2x)176 (+17%)166 (-34%)225 (-56%)431 (-54%)231 (-51%)3
ℹ️ 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
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
❌ Failed E2E Tests
▲ Vercel Production (8 failed)
python-node (8 failed):
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE | 🔍 observability
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04 | 🔍 observability
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH | 🔍 observability
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456 | 🔍 observability
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ | 🔍 observability
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD | 🔍 observability
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6 | 🔍 observability
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1 | 🔍 observability
🌐 Cross-language Conformance (9 failed)
python (9 failed):
  • deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M13767WFNN55ZPS08TTWYSE5
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1
⚠️ 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.
10 flaky tests
  • abortParallelWorkflow: abort cancels all parallel steps (nextjs-webpack)
  • addTenWorkflow (sveltekit)
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (example)
  • deploymentId: 'latest' is a no-op in non-Vercel worlds (sveltekit)
  • hookWithSleepFinalStepWorkflow - step only on final payload (nextjs-turbopack)
  • hookWorkflow (vite)
  • importMetaUrlWorkflow - import.meta.url is available in step bundles (nextjs-webpack)
  • negative startIndex (reads from end) (fastify)
  • resilient start: addTenWorkflow completes when run_created returns 500 (nextjs-webpack)
  • webhookWorkflow (nextjs-webpack)
🛠 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 (tanstack-start) · at 03:36:34Z · abandoned wrun_01M1370T9QXQY5DGPV7Z4MM7CP
  • cold-start-warmup · suite warmup (python) · at 03:37:00Z · abandoned wrun_41M136YSW40GKY4DAMXP7CRT1J · (+6 more)
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:17Z · abandoned wrun_41M1372EW50GP2RNA9ZW12DSYM
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHJ0GYNMQ8EVS4VP59M
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRH
  • run-pickup-stall · sleepingWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRG
  • run-pickup-stall · nullByteWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHY0GNNW85TFDYFH6GT
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:49Z · abandoned wrun_41M1373E6A0GJJ736KSC91PHV8
  • cold-start-warmup · suite warmup (python) · at 03:37:49Z · abandoned wrun_01M13709F0CFVSSEQJ675KSV3N · (+7 more)
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKFV76GYY90JWAWA3H9
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKMJ95Q6FMXD9S91BZG
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:38:04Z · abandoned wrun_01M1373YKE0BJMG4K9KG19CQX7
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKRHSVK59E9BRNVXXWE
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKPQN9NRWNT72VZEK34
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SV0GZC31F122EX6ZA3
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749RC0GPK46HWB57ZK200
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749VJ0GXV6SVWDJE8Z8H5
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SK0GV08Z70ZBF8ADQE
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:38:58Z · abandoned wrun_41M1374D540GRDSCRGRXRTA0VJ
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:39:04Z · abandoned wrun_01M1375S74279D328PFRY93Q2E
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7AC88CCJ5Y13RECB57
  • run-pickup-stall · sleepingWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7C45FBF9CDSBCCAF55
  • run-pickup-stall · nullByteWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7J24TG2XANEEE3438V
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7FD9PG9WVJZT46G7CB
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:04Z · abandoned wrun_01M1377KTQJY02FZSJCAAC8B4B
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:05Z · abandoned wrun_01M1377KV0R0Z2F0DH4JVMP0HS
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:05Z · abandoned wrun_01M1377KV2E6YE3WGEJJTA2ER5
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H61VC8V106V4YWDTXM3
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H6DX7Y9CPGV467FHRFT
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:48Z · abandoned wrun_41M13771MX0GS1A8AX87B70570
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:48Z · abandoned wrun_41M137751P0GQHEK8MZJP94DPC
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:41:04Z · abandoned wrun_01M1379EE7EG775GYHVRPWY4GB
E2E Test Summary
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production357087424320
✅ 💻 Local Development392205584480
✅ 📦 Local Production392205584480
✅ 🐘 Local Postgres392205584480
✅ 🪟 Windows32000320
❌ 🌐 Cross-language Conformance09132141
✅ vercel-http-transport8170143960
✅ vercel-multi-region270027
✅ vercel-ws-transport553087640
Total1705317277819848
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro-node132028
✅ astro-quickjs132028
✅ example-node132028
✅ example-quickjs132028
✅ express-node132028
✅ express-quickjs132028
✅ fastify-node132028
✅ fastify-quickjs132028
✅ hono-node132028
✅ hono-quickjs132028
✅ nest-node132028
✅ nest-quickjs132028
✅ nextjs-turbopack-node15703
✅ nextjs-turbopack-quickjs15703
✅ nextjs-webpack-node15703
✅ nextjs-webpack-quickjs15703
✅ nitro-node132028
✅ nitro-quickjs132028
✅ nuxt-node132028
✅ nuxt-quickjs132028
❌ python-node08152
✅ sveltekit-node15109
✅ sveltekit-quickjs15109
✅ tanstack-start-node132028
✅ tanstack-start-quickjs132028
✅ vite-node132028
✅ vite-quickjs132028
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack-node16000
✅ nextjs-turbopack-quickjs16000
❌ 🌐 Cross-language Conformance
AppPassedFailedSkipped
❌ python09132
✅ vercel-http-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ hono132028
✅ nextjs-turbopack15703
✅ nitro132028
✅ vite132028
✅ vercel-multi-region
AppPassedFailedSkipped
✅ nextjs-turbopack2700
✅ vercel-ws-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ nextjs-turbopack15703
✅ vite132028
📋 View full workflow run
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Sim World
Simulated world deterministic testing for races. Traces
🟠 world-sim scenario book — 1 fail of 41 total
fence=per-spec
scenariooutcomeeventsvirtreplayviolations
✅ smoke-no-stepscompleted30msok0
✅ smoke-one-stepcompleted60msok0
✅ hook-at-step-startedcompleted120msok0
✅ hook-at-step-completedcompleted120msok0
✅ hook-at-hook-createdcompleted120msok0
✅ deadline-hook-winscompleted71.0hok0
✅ deadline-expirescompleted71.0hok0
✅ long-sleepcompleted1130.0dok0
✅ hook-never-arrivesstalled30msskipped0
✅ step-retries-twicecompleted102.0sok0
✅ parallel-stepscompleted90msok0
✅ hook-on-execution-statecompleted120msok0
✅ peek-hook-before-branchcompleted120msok0
✅ peek-hook-after-branchcompleted120msok0
✅ peek-hook-at-registrationcompleted120msok0
✅ race-hook-before-probecompleted120msok0
✅ race-hook-after-probecompleted120msok0
✅ race-duplicate-deliverycompleted130msok0
✅ attr-hook-before-stepcompleted110msok0
✅ attr-hook-after-stepcompleted110msok0
✅ attr-from-step-bodycompleted130msok0
✅ fork-hook-after-timeoutcompleted141.0mok0
✅ fork-hook-before-timeoutcompleted141.0mok0
✅ count-hook-after-timeoutcompleted171.0mok0
✅ count-hook-before-timeoutcompleted201.0mok0
✅ stale-read-step-count-forkcompleted201.0mok0
✅ stale-read-equal-step-countscompleted141.0mok0
✅ step-vs-step-forkcompleted120msok0
✅ step-vs-step-fork-fencedcompleted120msok0
✅ fence-catches-benign-directioncompleted125msok0
✅ in-flight-before-decisioncompleted171.0mok0
❌ in-flight-before-decision-countedcompleted171.0mok0
✅ in-flight-after-decisioncompleted192.0mok0
✅ stale-read-step-count-fork-fencedcompleted201.0mok0
✅ fork-hook-winscompleted131.0mok0
✅ fork-timeout-winscompleted131.0mok0
✅ unclaimed-payload-under-forkcompleted171.0mok0
✅ claimed-payload-under-forkcompleted171.0mok0
✅ writers-independent-step-bodiescompleted120msok0
✅ writers-scripted-tempocompleted120msok0
✅ cancel-mid-stepcancelled70msskipped0
Full trace: world-sim.txt
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
FrameworkFlow routeStep reg.Framework output
hono200.9 KiB (±0)40.3 KiB (+27 B)1.76 MiB (+753 B)
nextjs-turbopack206.3 KiB (±0)439 B (±0)763.7 KiB (+206 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.
1d5f28b · run
shalabhc
shalabhc
approved these changes
Aug 28, 2026
View reviewed changes
@shalabhcshalabhc
left a comment


Copy link


Copy Markdown

Collaborator
Choose a reason for hiding this comment

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

changeset looks too large tho
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment thread.changeset/quiet-normal-execution-logs.md
Outdated

'@workflow/world': patch
---

Stop logging on healthy workflow execution. A successful run now prints nothing;
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

make this more terse (see the other changlogs. should just be one-two line. not a story)
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

Trimmed to two sentences in 1d5f28b — matches the AGENTS.md guidance (one sentence, two at most) and the length of the other changelogs. The per-log-site rationale stays in the PR description. Package list and bump types are unchanged.
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment threadpackages/world-local/src/queue.ts
 // Debug-gated: this is the semaphore doing its job. A fan-out wider
 // than the limit queues behind it and every message still runs, so a
 // per-message warning turns a healthy wide run into a wall of output.
 debugLog(
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

nice fix!
@vercel@pranaygp
Trim the changeset to two sentences
1d5f28b
Review feedback: the changeset read as a story. AGENTS.md asks for one
sentence, or two at most; the per-log-site rationale already lives in the
PR description. Package list and bump types are unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
merged commit ffc5807
into
mainAug 28, 2026

181 of 183 checks passed

@pranaygp
pranaygp
deleted the

quiet-workflow-logs

branch
August 28, 2026 03:45
@github-actions
github-actionsBot
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
No backport to stable for ffc5807 (AI decision).
This is log-noise cleanup, not a stability fix: it changes existing logging behavior (warn/log downgraded to a DEBUG-gated debug line) and adds new public API surface (debugLog / isWorkflowDebugEnabled exported from @workflow/utils), with no correctness, crash, or resource issue being fixed. Its stated motivation is also largely main-only — packages/world-vercel/src/ws-transport.ts and docs/content/worlds/ do not exist on origin/stable, so the WebSocket-default fallout that drove the change does not affect the maintenance line. The residual bits that do apply on stable (packages/utils/src/get-port.ts, packages/world-local/src/queue.ts, packages/world/src/recovery.ts) are cosmetic verbosity changes that stable users can live without.
To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:
ffc58078d0c3cd2786d69bab7e41614566a9ea4e


This was referenced Aug 28, 2026
 Open

 Open

 Open

 Open

 Open

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

Reviewers

@shalabhcshalabhcshalabhc approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@pranaygp@shalabhc

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
})();
Stop logging on healthy workflow execution by pranaygp · Pull Request #3878 · vercel/workflow · GitHub
Skip to content
Stop logging on healthy workflow execution - #3878
Merged
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Aug 28, 2026
Merged
Stop logging on healthy workflow execution#3878
pranaygp merged 2 commits into
mainfrom 
quiet-workflow-logs
Conversation
@pranaygp
@pranaygppranaygp
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
What
Normal workflow execution should print nothing. Today a healthy run emits several lines that only describe the runtime working correctly.
Most of it is fallout from #3702, which defaulted the events transport to WebSockets. Three log sites written while the transport was opt-in became default-path output, because each one reports a choice the caller no longer makes:
LineWhy it was fine when WS was opt-inWhy it is noise now
world-vercel: using ws events transport (…)Confirmed the flag took effectRuns once per cold start on every deployment, naming the transport it was always going to use
…requested but a World with projectConfig … falling backA real mismatch: someone asked for WS and didn't get itNobody asks now, so every CLI command and the observability app — all projectConfig Worlds — warn about a fallback they neither chose nor can act on
…received a drain notice (reason: max_duration…)Rare while few sockets existedmax_duration and auth_expiry are routine; the transport reconnects from the close that follows and no write is lost
Swept for the same shape elsewhere and found three more:
  • world-local queue concurrency — warned per message once a fan-out exceeded the limit. That is the semaphore doing its job; every message still runs.
  • @workflow/world active-run recovery — printed on every dev-server restart with work in flight. Resuming active runs is what a restart is for.
  • @workflow/utils port detection — two diagnostics gated on NODE_ENV=development, which is the only environment that reaches this code, so the gate made them unconditional for their entire audience. The getWorkflowPort one fires on an ordinary startup race (dev server still compiling its workflow routes) that the fallback then resolves correctly.
How
A new debugLog in @workflow/utils gates on DEBUG=workflow:* (or *), the same selector @workflow/core's logger already uses, so these join world-vercel's existing httpLog and logRetry output under one switch. It reads DEBUG per call rather than at module load, since Worlds are built long after import. @workflow/world hand-rolls the same check — that package deliberately carries no workspace dependencies, matching how env-config.ts hand-rolls globalSingleton().
Nothing about error logging changed. Every console.error / console.warn on a genuine fault is untouched, including the ws-transport's "failures are never silent" set and the re-enqueue failure sitting directly above the recovery line that did get gated — that one leaves a run unresumed. logger.warn / logger.error in @workflow/core still print unconditionally.
Testing
  • packages/{utils,world,world-local,world-vercel}/src — 1449 passed, 4 skipped.
  • packages/core/src — 2268 passed (unchanged; core consumes @workflow/utils).
  • New coverage: debug-log.test.ts (off by default, accepts workflow:* / *, ignores another library's selector, re-reads per call); ws-transport tests split into DEBUG / no-DEBUG pairs; recovery tests assert a successful recovery logs at no level while a failed re-enqueue still warns without DEBUG.
  • Verified the new ws-transport assertions bite: reverting ws-transport.ts alone fails exactly 4 of them.
  • biome check on the changed files reports the same 7 pre-existing warnings as base (exit 0); turbo typecheck clean for all four packages.
Two packages/utils/src/check-data-dir.test.ts cases fail on this machine on unmodified main as well — a leftover gitignored .workflow-data at the repo root that the test walks up and finds. Unrelated to this change.
Docs
worlds/v5/vercel.mdx claimed the projectConfig fallback logs a warning once per process. Updated to say it is silent and reported under DEBUG, and to point at workflow.events.transport on the per-write span as the durable answer to which transport carried a run.
🤖 Generated with Claude Code
@vercel@pranaygp
Stop logging on healthy workflow execution
64343e9
A successful run printed several lines that described the runtime working
correctly. Most of it was fallout from defaulting the events transport to
WebSockets (#3702): three breadcrumbs written while the transport was opt-in
became default-path output, because each one reported a choice the caller no
longer makes.
- `world-vercel: using ws events transport (…)` ran once per cold start on
every deployment, naming the transport it was always going to use.
- The `projectConfig` proxy fallback warned once per process. That World cannot
hold a socket, so with WS on by default every CLI command and the
observability app warned about a fallback nobody asked for and nobody can act
on. Debug-gated and reworded from "requested but" to "unavailable for".
- The `max_duration` / `auth_expiry` drain notice is routine: the transport
reconnects from the close that follows and no write is lost.
Swept for the same shape elsewhere:
- `world-local`'s queue-concurrency notice fired per message once a fan-out
exceeded the limit — the semaphore doing its job.
- `@workflow/world`'s active-run recovery line printed on every dev-server
restart with work in flight. The re-enqueue *failure* above it stays
unconditional; that one leaves a run unresumed.
- The port-detection diagnostics in `@workflow/utils` keyed off
`NODE_ENV=development`, which is the only environment that reaches them, so
the gate made them unconditional for their whole audience.
All of it moves behind `DEBUG=workflow:*` via a new `debugLog` in
`@workflow/utils`, joining world-vercel's existing `httpLog` and `logRetry`
output under one selector. Warnings and errors are untouched, so a run that
actually goes wrong is no quieter than before — the ws-transport tests that
assert failures are never silent still pass unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
requested a review
from a team
as a code ownerAugust 28, 2026 01:22
@changeset-bot
changeset-botBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

🦋 Changeset detected
Latest commit: 1d5f28b
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 23 packages
NameType
@workflow/world-vercelPatch
@workflow/world-localPatch
@workflow/utilsPatch
@workflow/worldPatch
@workflow/cliPatch
@workflow/corePatch
@workflow/webPatch
@workflow/vitestPatch
@workflow/world-postgresPatch
@workflow/aiPatch
@workflow/buildersPatch
@workflow/errorsPatch
@workflow/nestPatch
@workflow/web-sharedPatch
workflowPatch
@workflow/world-testingPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/astroPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch
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
vercelBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
The latest updates on your projects. Learn more about Vercel for GitHub.
ProjectDeploymentActionsUpdated (UTC)
example-nextjs-workflow-turbopackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-nextjs-workflow-webpackReadyReadyPreview, v0Aug 28, 2026 3:36am
example-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-astro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-express-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-fastify-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-hono-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nestjs-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nitro-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-nuxt-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-python-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-sveltekit-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-tanstack-start-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workbench-vite-workflowReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-docsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-swc-playgroundReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-tarballsReadyReadyPreview, v0Aug 28, 2026 3:36am
workflow-webReadyReadyPreview, v0Aug 28, 2026 3:36am
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
📊 Workflow Benchmarks
commit 1d5f28b · Fri, 28 Aug 2026 03:59:15 GMT · run logs
Backend: vercel · app: nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep658 (+250%) 🔻1372 🔴 (+23%) 🔻1411 🔴 (+23%) 🔻1544 🔴 (+6.0%)30
TTFSstream934 (+480%) 🔻1455 🔴 (+29%) 🔻1525 🔴 (+32%) 🔻1626 🔴 (+20%) 🔻30
TTFShook + stream1720 (+44%) 🔻1812 🔴 (+31%) 🔻1844 🔴 (+27%) 🔻1982 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)714 (+9.8%)2184 (+24%) 🔻2215 (+15%) 🔻2950 (+40%) 🔻10
Fan-out TTLSPromise.all(100 steps)2155 (+15%) 🔻4016 (+8.0%)4073 (+6.9%)10458 (+51%) 🔻10
STSO1020 steps (inline)133 (+22%) 🔻153 (-3.8%)172 (-7.0%)235 (-18%) 💚1019
WO1020 steps155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)155504 (+1.1%)1
CRTTfirst chunk (pooled)113 (+19%) 🔻146 (-8.2%)200 (+0.5%)238 (-29%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)139 (+2%)164 (-10%)265 (+7%)522 (-4%)144 (-22%)10
size sweep (100/s, 160B-12KB)137 (+5%)187 (-12%)263 (-55%)405 (-54%)119 (-44%)10
replay gateway-gpt-5.4-nano-2000t (1x)133 (-2%)149 (-16%)182 (-24%)890 (+115%)377 (+15%)3
replay eve-gpt-5.6-sol-2000t (1x)136 (-5%)155 (-16%)198 (-31%)370 (-46%)297 (-53%)2
replay eve-gpt-5.6-sol-2000t (2x)148 (-1%)214 (-15%)452 (-12%)1144 (+22%)344 (-28%)3
📈 STSO distribution vs main (inline / queue-hop histograms)
1020 steps (inline)
Cumulative STSO time: main 153650ms → this run 155201ms (Δ +1551ms, +1%)
100-150 ms ███████████████████████┃ main 681 this 687 +6
150-200 ms █████████░┃ main 264 this 302 +38
200-250 ms ┃█ main 52 this 23 -29
250-300 ms ┃ main 15 this 5 -10
300-350 ms ┃ main 5 this 0 -5
350-400 ms ┃ main 2 this 0 -2
400-450 ms ┃ main 0 this 2 +2

📈 CRTT drill-down vs main (RTT distributions & profiles)
variant RTT 1ms→5s+ avg p50 p90 p99 n
control ······▂█▁▁··· 143 (-6%) 129 (-7%) 265 (+7%) 522 (-4%) 3000
sweep ······▂█▂···· 142 (-25%) 127 (-6%) 263 (-55%) 405 (-54%) 3000
gw 1x ·····▁▂█▁▁▁·· 140.4 (-6%) 127 (-5%) 182 (-24%) 890 (+115%) 5295
eve 1x ·····▁▃█▂▁··· 132.5 (-18%) 120 (-13%) 198 (-31%) 370 (-46%) 5186
eve 2x ·····▁▁█▃▁▁·· 179.4 (-19%) 150 (-14%) 452 (-12%) 1144 (+22%) 7779

RTT over stream progress (avg per tenth of stream, bars scaled min→max):
control ██▃▃▃▁█▅▂▂ 126–164ms
sweep █▅▅▃▃▂▁▂▃▂ 120–185ms
gw 1x ▂▁▁▁▁▃▂▁▁█ 123–233ms
eve 1x ▇▅▄▄▁▄▅█▆▇ 111–148ms
eve 2x ▁▁▁▂▁▂▃█▇▂ 140–295ms

RTT by chunk size (avg per log size bin, ~160B → ~12KB serialized, bars scaled min→max):
sweep ▁▁▃█▆▅▃ 140–145ms

Delivery jitter over stream progress (avg positive CDV per tenth of stream, bars scaled min→max):
control ▁▅▅▄▃▆█▄▇▆ 39–49ms
sweep ▁▃█▅▇▅▄▆▄▅ 43–67ms
gw 1x ▂▂▂▁▂▅▆▃▂█ 37–56ms
eve 1x █▇▃▃▁▅▄▆▃▇ 21–29ms
eve 2x ▃█▁▄▅▃▂▅▄▆ 23–31ms

📜 Previous results (1)
64343e9
Fri, 28 Aug 2026 01:46:43 GMT · run logs
vercel / nextjs-turbopack
MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep183 (-2.7%)1314 🔴 (+18%) 🔻1383 🔴 (+20%) 🔻1480 🔴 (+1.6%)30
TTFSstream168 (+4.3%)1297 🔴 (+15%)1338 🔴 (+16%) 🔻1442 🔴 (+6.3%)30
TTFShook + stream1471 (+23%) 🔻1588 🔴 (+14%)1742 🔴 (+20%) 🔻1983 🔴 (+30%) 🔻30
Fan-out TTFSPromise.all(100 steps)719 (+11%)2304 (+31%) 🔻2698 (+40%) 🔻2780 (+32%) 🔻10
Fan-out TTLSPromise.all(100 steps)1944 (+4.2%)4184 (+13%)4225 (+11%)9030 (+30%) 🔻10
STSO1020 steps (inline)101 (-7.3%)149 (-6.3%)179 (-3.2%)299 (+4.5%)1019
WO1020 steps146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)146141 (-5.0%)1
CRTTfirst chunk (pooled)97 (+2.1%)137 (-14%)176 (-12%)196 (-41%) 💚28
Streams
ScenarioCRTT 1stp75p90p99CDV maxiters
paced control (100/s, 60B)122 (-10%)140 (-23%)203 (-18%)493 (-10%)114 (-38%)10
size sweep (100/s, 160B-12KB)127 (-3%)140 (-34%)195 (-67%)7053 (+695%)109 (-49%)10
replay gateway-gpt-5.4-nano-2000t (1x)119 (-12%)130 (-27%)186 (-22%)908 (+120%)224 (-32%)3
replay eve-gpt-5.6-sol-2000t (1x)124 (-14%)134 (-28%)179 (-38%)397 (-42%)331 (-48%)2
replay eve-gpt-5.6-sol-2000t (2x)176 (+17%)166 (-34%)225 (-56%)431 (-54%)231 (-51%)3
ℹ️ 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
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
🧪 E2E Test Results
❌ Some tests failed
❌ Failed E2E Tests
▲ Vercel Production (8 failed)
python-node (8 failed):
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE | 🔍 observability
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04 | 🔍 observability
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH | 🔍 observability
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456 | 🔍 observability
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ | 🔍 observability
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD | 🔍 observability
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6 | 🔍 observability
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1 | 🔍 observability
🌐 Cross-language Conformance (9 failed)
python (9 failed):
  • deploymentId: 'latest' is a no-op in non-Vercel worlds | wrun_01M13767WFNN55ZPS08TTWYSE5
  • promiseAllWorkflow | wrun_41M136Z8P10GRC0SJF1YC8MBGE
  • sleepingWorkflow | wrun_41M136ZZNJ0GQMPXX1SAFTJS04
  • parallelSleepWorkflow | wrun_41M13700GX0GYGMZFWF6EDNYHH
  • nullByteWorkflow | wrun_41M13708KN0GK5C113KCQZV456
  • cancelRun - cancelling a running workflow | wrun_41M137561J0GW1J0PY8TD9M9VJ
  • cancelRun via CLI - cancelling a running workflow | wrun_41M13756460GV7JEFT60WYFTXD
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_41M1375FTV0GQ72S60REJSVPF6
  • resilient start: addTenWorkflow completes when run_created returns 500 | wrun_41M137619A0GW8J0MTKDCPHSX1
⚠️ 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.
10 flaky tests
  • abortParallelWorkflow: abort cancels all parallel steps (nextjs-webpack)
  • addTenWorkflow (sveltekit)
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously (example)
  • deploymentId: 'latest' is a no-op in non-Vercel worlds (sveltekit)
  • hookWithSleepFinalStepWorkflow - step only on final payload (nextjs-turbopack)
  • hookWorkflow (vite)
  • importMetaUrlWorkflow - import.meta.url is available in step bundles (nextjs-webpack)
  • negative startIndex (reads from end) (fastify)
  • resilient start: addTenWorkflow completes when run_created returns 500 (nextjs-webpack)
  • webhookWorkflow (nextjs-webpack)
🛠 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 (tanstack-start) · at 03:36:34Z · abandoned wrun_01M1370T9QXQY5DGPV7Z4MM7CP
  • cold-start-warmup · suite warmup (python) · at 03:37:00Z · abandoned wrun_41M136YSW40GKY4DAMXP7CRT1J · (+6 more)
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:17Z · abandoned wrun_41M1372EW50GP2RNA9ZW12DSYM
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHJ0GYNMQ8EVS4VP59M
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRH
  • run-pickup-stall · sleepingWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHT0GM1MESE8HN75ZRG
  • run-pickup-stall · nullByteWorkflow (python) · at 03:37:17Z · abandoned wrun_41M1372EHY0GNNW85TFDYFH6GT
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:37:49Z · abandoned wrun_41M1373E6A0GJJ736KSC91PHV8
  • cold-start-warmup · suite warmup (python) · at 03:37:49Z · abandoned wrun_01M13709F0CFVSSEQJ675KSV3N · (+7 more)
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKFV76GYY90JWAWA3H9
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKMJ95Q6FMXD9S91BZG
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:38:04Z · abandoned wrun_01M1373YKE0BJMG4K9KG19CQX7
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKRHSVK59E9BRNVXXWE
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:04Z · abandoned wrun_01M1373YKPQN9NRWNT72VZEK34
  • run-pickup-stall · sleepingWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SV0GZC31F122EX6ZA3
  • run-pickup-stall · nullByteWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749RC0GPK46HWB57ZK200
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749VJ0GXV6SVWDJE8Z8H5
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:38:17Z · abandoned wrun_41M13749SK0GV08Z70ZBF8ADQE
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:38:58Z · abandoned wrun_41M1374D540GRDSCRGRXRTA0VJ
  • run-pickup-stall · deploymentId: 'latest' is a no-op in non-Vercel worlds (python) · at 03:39:04Z · abandoned wrun_01M1375S74279D328PFRY93Q2E
  • run-pickup-stall · promiseAllWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7AC88CCJ5Y13RECB57
  • run-pickup-stall · sleepingWorkflow (python) · at 03:39:04Z · abandoned wrun_01M1375S7C45FBF9CDSBCCAF55
  • run-pickup-stall · nullByteWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7J24TG2XANEEE3438V
  • run-pickup-stall · parallelSleepWorkflow (python) · at 03:39:05Z · abandoned wrun_01M1375S7FD9PG9WVJZT46G7CB
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:04Z · abandoned wrun_01M1377KTQJY02FZSJCAAC8B4B
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:05Z · abandoned wrun_01M1377KV0R0Z2F0DH4JVMP0HS
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:05Z · abandoned wrun_01M1377KV2E6YE3WGEJJTA2ER5
  • run-pickup-stall · cancelRun - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H61VC8V106V4YWDTXM3
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:35Z · abandoned wrun_01M1378H6DX7Y9CPGV467FHRFT
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:40:48Z · abandoned wrun_41M13771MX0GS1A8AX87B70570
  • run-pickup-stall · cancelRun via CLI - cancelling a running workflow (python) · at 03:40:48Z · abandoned wrun_41M137751P0GQHEK8MZJP94DPC
  • run-pickup-stall · sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration (python) · at 03:41:04Z · abandoned wrun_01M1379EE7EG775GYHVRPWY4GB
E2E Test Summary
Summary
PassedFailedSkippedTotal
❌ ▲ Vercel Production357087424320
✅ 💻 Local Development392205584480
✅ 📦 Local Production392205584480
✅ 🐘 Local Postgres392205584480
✅ 🪟 Windows32000320
❌ 🌐 Cross-language Conformance09132141
✅ vercel-http-transport8170143960
✅ vercel-multi-region270027
✅ vercel-ws-transport553087640
Total1705317277819848
Details by Category
❌ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro-node132028
✅ astro-quickjs132028
✅ example-node132028
✅ example-quickjs132028
✅ express-node132028
✅ express-quickjs132028
✅ fastify-node132028
✅ fastify-quickjs132028
✅ hono-node132028
✅ hono-quickjs132028
✅ nest-node132028
✅ nest-quickjs132028
✅ nextjs-turbopack-node15703
✅ nextjs-turbopack-quickjs15703
✅ nextjs-webpack-node15703
✅ nextjs-webpack-quickjs15703
✅ nitro-node132028
✅ nitro-quickjs132028
✅ nuxt-node132028
✅ nuxt-quickjs132028
❌ python-node08152
✅ sveltekit-node15109
✅ sveltekit-quickjs15109
✅ tanstack-start-node132028
✅ tanstack-start-quickjs132028
✅ vite-node132028
✅ vite-quickjs132028
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable-node134026
✅ astro-stable-quickjs134026
✅ express-stable-node134026
✅ express-stable-quickjs134026
✅ fastify-stable-node134026
✅ fastify-stable-quickjs134026
✅ hono-stable-node134026
✅ hono-stable-quickjs134026
✅ nest-stable-node134026
✅ nest-stable-quickjs134026
✅ nextjs-turbopack-canary-node141019
✅ nextjs-turbopack-canary-quickjs141019
✅ nextjs-turbopack-stable-node16000
✅ nextjs-turbopack-stable-quickjs16000
✅ nextjs-webpack-canary-node141019
✅ nextjs-webpack-canary-quickjs141019
✅ nextjs-webpack-stable-node16000
✅ nextjs-webpack-stable-quickjs16000
✅ nitro-stable-node134026
✅ nitro-stable-quickjs134026
✅ nuxt-stable-node134026
✅ nuxt-stable-quickjs134026
✅ sveltekit-stable-node15307
✅ sveltekit-stable-quickjs15307
✅ tanstack-start-node134026
✅ tanstack-start-quickjs134026
✅ vite-stable-node134026
✅ vite-stable-quickjs134026
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack-node16000
✅ nextjs-turbopack-quickjs16000
❌ 🌐 Cross-language Conformance
AppPassedFailedSkipped
❌ python09132
✅ vercel-http-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ hono132028
✅ nextjs-turbopack15703
✅ nitro132028
✅ vite132028
✅ vercel-multi-region
AppPassedFailedSkipped
✅ nextjs-turbopack2700
✅ vercel-ws-transport
AppPassedFailedSkipped
✅ example132028
✅ express132028
✅ nextjs-turbopack15703
✅ vite132028
📋 View full workflow run
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
Sim World
Simulated world deterministic testing for races. Traces
🟠 world-sim scenario book — 1 fail of 41 total
fence=per-spec
scenariooutcomeeventsvirtreplayviolations
✅ smoke-no-stepscompleted30msok0
✅ smoke-one-stepcompleted60msok0
✅ hook-at-step-startedcompleted120msok0
✅ hook-at-step-completedcompleted120msok0
✅ hook-at-hook-createdcompleted120msok0
✅ deadline-hook-winscompleted71.0hok0
✅ deadline-expirescompleted71.0hok0
✅ long-sleepcompleted1130.0dok0
✅ hook-never-arrivesstalled30msskipped0
✅ step-retries-twicecompleted102.0sok0
✅ parallel-stepscompleted90msok0
✅ hook-on-execution-statecompleted120msok0
✅ peek-hook-before-branchcompleted120msok0
✅ peek-hook-after-branchcompleted120msok0
✅ peek-hook-at-registrationcompleted120msok0
✅ race-hook-before-probecompleted120msok0
✅ race-hook-after-probecompleted120msok0
✅ race-duplicate-deliverycompleted130msok0
✅ attr-hook-before-stepcompleted110msok0
✅ attr-hook-after-stepcompleted110msok0
✅ attr-from-step-bodycompleted130msok0
✅ fork-hook-after-timeoutcompleted141.0mok0
✅ fork-hook-before-timeoutcompleted141.0mok0
✅ count-hook-after-timeoutcompleted171.0mok0
✅ count-hook-before-timeoutcompleted201.0mok0
✅ stale-read-step-count-forkcompleted201.0mok0
✅ stale-read-equal-step-countscompleted141.0mok0
✅ step-vs-step-forkcompleted120msok0
✅ step-vs-step-fork-fencedcompleted120msok0
✅ fence-catches-benign-directioncompleted125msok0
✅ in-flight-before-decisioncompleted171.0mok0
❌ in-flight-before-decision-countedcompleted171.0mok0
✅ in-flight-after-decisioncompleted192.0mok0
✅ stale-read-step-count-fork-fencedcompleted201.0mok0
✅ fork-hook-winscompleted131.0mok0
✅ fork-timeout-winscompleted131.0mok0
✅ unclaimed-payload-under-forkcompleted171.0mok0
✅ claimed-payload-under-forkcompleted171.0mok0
✅ writers-independent-step-bodiescompleted120msok0
✅ writers-scripted-tempocompleted120msok0
✅ cancel-mid-stepcancelled70msskipped0
Full trace: world-sim.txt
@github-actions
github-actionsBot
commented
Aug 28, 2026•

edited

Loading

Copy link


Copy Markdown

Contributor
FrameworkFlow routeStep reg.Framework output
hono200.9 KiB (±0)40.3 KiB (+27 B)1.76 MiB (+753 B)
nextjs-turbopack206.3 KiB (±0)439 B (±0)763.7 KiB (+206 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.
1d5f28b · run
shalabhc
shalabhc
approved these changes
Aug 28, 2026
View reviewed changes
@shalabhcshalabhc
left a comment


Copy link


Copy Markdown

Collaborator
Choose a reason for hiding this comment

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

changeset looks too large tho
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment thread.changeset/quiet-normal-execution-logs.md
Outdated

'@workflow/world': patch
---

Stop logging on healthy workflow execution. A successful run now prints nothing;
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

make this more terse (see the other changlogs. should just be one-two line. not a story)
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

Trimmed to two sentences in 1d5f28b — matches the AGENTS.md guidance (one sentence, two at most) and the length of the other changelogs. The per-log-site rationale stays in the PR description. Package list and bump types are unchanged.
pranaygp
pranaygp
commented
Aug 28, 2026
View reviewed changes
Comment threadpackages/world-local/src/queue.ts
 // Debug-gated: this is the semaphore doing its job. A fan-out wider
 // than the limit queues behind it and every message still runs, so a
 // per-message warning turns a healthy wide run into a wall of output.
 debugLog(
@pranaygppranaygpAug 28, 2026

Copy link


Copy Markdown

ContributorAuthor
Choose a reason for hiding this comment

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

nice fix!
@vercel@pranaygp
Trim the changeset to two sentences
1d5f28b
Review feedback: the changeset read as a story. AGENTS.md asks for one
sentence, or two at most; the per-log-site rationale already lives in the
PR description. Package list and bump types are unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Pranay Prakash <1797812+pranaygp@users.noreply.github.com>
@pranaygp
pranaygp
merged commit ffc5807
into
mainAug 28, 2026

181 of 183 checks passed

@pranaygp
pranaygp
deleted the

quiet-workflow-logs

branch
August 28, 2026 03:45
@github-actions
github-actionsBot
commented
Aug 28, 2026

Copy link


Copy Markdown

Contributor
No backport to stable for ffc5807 (AI decision).
This is log-noise cleanup, not a stability fix: it changes existing logging behavior (warn/log downgraded to a DEBUG-gated debug line) and adds new public API surface (debugLog / isWorkflowDebugEnabled exported from @workflow/utils), with no correctness, crash, or resource issue being fixed. Its stated motivation is also largely main-only — packages/world-vercel/src/ws-transport.ts and docs/content/worlds/ do not exist on origin/stable, so the WebSocket-default fallout that drove the change does not affect the maintenance line. The residual bits that do apply on stable (packages/utils/src/get-port.ts, packages/world-local/src/queue.ts, packages/world/src/recovery.ts) are cosmetic verbosity changes that stable users can live without.
To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:
ffc58078d0c3cd2786d69bab7e41614566a9ea4e


This was referenced Aug 28, 2026
 Open

 Open

 Open

 Open

 Open

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

Reviewers

@shalabhcshalabhcshalabhc approved these changes

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@pranaygp@shalabhc