Skip to content

[docs] Add a dynamic workflows cookbook recipe backed by e2e fixtures - #4541

Draft
alangenfeld wants to merge 11 commits into
mainfrom
alangenfeld/workflow-dynamic-workflows-cookbook
Draft

alangenfeld wants to merge 11 commits into
mainfrom
alangenfeld/workflow-dynamic-workflows-cookbook

Conversation

@alangenfeld

@alangenfeld alangenfeld commented Sep 30, 2026 •

Copy link
Copy Markdown
Collaborator

Summary & Motivation

A cookbook recipe for experimental dynamic workflows, built around an integration team publishing a reviewed, customer-specific CRM migration procedure after the platform has deployed — no application release per customer. It states when static configuration, a JSON plan, or a runtime agent is the better choice instead, and leads with the start(source, [input], { experimental_dynamic: { steps } }) call and the step-catalog contract, leaving the full procedure to an appendix.

  • The recipe's code is backed by fixtures: the migration catalog is a workbench step catalog over a pure simulated destination, and procedure A is byte-for-byte the source the e2e test runs.
  • Both procedures validate parent links (self-parent, cycle, missing, cross-family) and reject only the affected family; the adapter refuses setParent cycles and plans changed after staging.
  • The evidence boundary sits next to the adapter claims: the simulation is labelled, so the tests show replay of recorded step results and pause/resume, not destination-side dedup, reviewer notification, or process restarts.

Test Plan

Eight e2e cases cover the migration procedures end to end, asserting the resulting destination records, the rejected families and their reasons, and the adapter's refusals; the docs typecheck covers the recipe's samples. Locally the file passed 20/20 against a nextjs-turbopack dev server with dynamic workflows enabled.

Snippet → fixture

Recipe snippet Mirrored by
workflows/migration-steps.ts, lib/migration-catalog.ts migration catalog steps and MIGRATION_CATALOG in 99_e2e.ts (pure simulated destination)
lib/start-procedure.ts startMissionRevision in 99_e2e.ts
procedures/crm-parent-first.js (complete, and excerpt) PARENT_FIRST_SOURCE in e2e-dynamic-workflow.test.ts
procedures/crm-provisional-first.js (excerpt) PROVISIONAL_FIRST_SOURCE in e2e-dynamic-workflow.test.ts
lib/bind-revision.ts bindMissionRevision in 99_e2e.ts
start and review routes none; the e2e runner publishes revisions and calls getHookByToken/resumeHook directly

Docs Preview

Page v5
Cookbook: Dynamic Workflows (new) /cookbook/advanced/dynamic-workflows
Deploy once, publish later #deploy-once-publish-later
Another procedure #another-procedure-over-the-same-catalog
Complete example #complete-example
Cookbook index (new entry) /cookbook#advanced
Concept page (from #4550) /docs/advanced/dynamic-workflows
Errors for each gate #errors-for-each-gate
Enabling storage on Vercel #enabling-storage-on-vercel

@changeset-bot

changeset-bot Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 9bc079b

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

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

vercel Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
example-nextjs-workflow-turbopack Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
example-nextjs-workflow-webpack Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
example-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-astro-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-express-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-fastify-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-hono-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-nestjs-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-nitro-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-nuxt-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-python-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-sveltekit-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-tanstack-start-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workbench-vite-workflow Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workflow-docs Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workflow-swc-playground Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workflow-tarballs Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC
workflow-web Ready Ready Preview, v0 Oct 2, 2026 8:43pm UTC

@github-actions

github-actions Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 9bc079b · Fri, 02 Oct 2026 21:06:51 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 2239 (+37%) 🔻 2412 🔴 (+37%) 🔻 2461 🔴 (+35%) 🔻 2650 🔴 (+7.6%) 30
TTFS stream 567 (-66%) 💚 2369 🔴 (+35%) 🔻 2398 🔴 (+34%) 🔻 2503 🔴 (+28%) 🔻 30
TTFS hook + stream 2563 (+68%) 🔻 2718 🔴 (+15%) 2775 🔴 (+9.3%) 2901 🔴 (-39%) 💚 30
Fan-out TTFS Promise.all(100 steps) 679 (+14%) 897 (-22%) 💚 1218 (-11%) 2840 (+31%) 🔻 10
Fan-out TTLS Promise.all(100 steps) 2536 (+15%) 3373 (-57%) 💚 3451 (-69%) 💚 9700 (-42%) 💚 10
STSO 1020 steps (inline) 140 (+22%) 🔻 172 (+23%) 🔻 188 (+18%) 🔻 242 (+16%) 🔻 1019
WO 1020 steps 170147 (+20%) 🔻 170147 (+20%) 🔻 170147 (+20%) 🔻 170147 (+20%) 🔻 1
CRTT first chunk (pooled) 73 (+22%) 🔻 99 (-16%) 💚 111 (-32%) 💚 131 (-95%) 💚 28

Streams

Scenario CRTT 1st p75 p90 p99 CDV max iters
paced control (100/s, 60B) 97.5 (+34%) 163 (+16%) 196 (-8%) 351 (-18%) 132 (-20%) 10
size sweep (100/s, 160B-12KB) 89 (-23%) 158 (-6%) 192 (-77%) 316 (-87%) 134 (+7%) 10
replay gateway-gpt-5.4-nano-2000t (1x) 92 (-12%) 155 (+16%) 188 (+6%) 249 (-74%) 135 (-66%) 3
replay eve-gpt-5.6-sol-2000t (1x) 73.5 (-25%) 148 (+6%) 181 (+3%) 227 (-28%) 175 (-37%) 2
replay eve-gpt-5.6-sol-2000t (2x) 99 (-16%) 197 (-100%) 240 (-99%) 319 (-99%) 218 (-98%) 3
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 141207ms → this run 169824ms (Δ +28617ms, +20%)

100-150 ms  █┃█████████████████████   main 858  this  58  -800
150-200 ms  ████░░░░░░░░░░░░░░░░░░░┃  main 147  this 908  +761
200-250 ms  ┃                         main  12  this  44   +32
250-300 ms  ┃                         main   2  this   6    +4
400-450 ms  ┃                         main   0  this   3    +3
📈 CRTT drill-down vs main (RTT distributions & profiles)
variant  RTT 1ms→5s+             avg         p50         p90         p99     n
control  ······▂█▁····  141.7 (+18%)  138 (+34%)   196 (-8%)  351 (-18%)  3000
sweep    ······▂█▁····  135.1 (-43%)  130 (+20%)  192 (-77%)  316 (-87%)  3000
gw 1x    ······▂█▁····   130.7 (+7%)  127 (+23%)   188 (+6%)  249 (-74%)  5295
eve 1x   ······▃█▁····  126.5 (+11%)  121 (+20%)   181 (+3%)  227 (-28%)  5186
eve 2x   ······▁█▂····  158.5 (-98%)  149 (-43%)  240 (-99%)  319 (-99%)  7779

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

control  ▂▁▂█▅▆█▇▂▂  132–152ms
sweep    ▅▁█▄▂▃▇▄▂▃  125–150ms
gw 1x    █▆▁▂▃▄▃▃▁▆  127–137ms
eve 1x   ▂▂▅▂▁▂█▆▆▁  119–140ms
eve 2x   ▂▁▂▃▁▃▅█▅▃  136–203ms

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

sweep  ▁▅██▇▃▃  133–136ms

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

control  ▅▁▆▅▅▅█▅▃▄  36–53ms
sweep    ▃▄█▁▁▂█▃▂▄  56–70ms
gw 1x    ▇▅▄▁▅▆▆█▅▅  35–44ms
eve 1x   ▃▅▆▆▁█▆█▄▅  22–27ms
eve 2x   ▆▇▁█▆▅▇▁▅▇  23–31ms
ℹ️ 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-2000t eaf22f5946e7c61f3c65c7006d550df180cfabd4e706254a09f22aec0cfb420d · gateway-gpt-5.4-nano-2000t 6f24ac518b6b83ff1d0e85a5fe78230db192716d66a7fc6b2fe022752001d041

🔴 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-actions Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

❌ Some tests failed

❌ Failed E2E Tests

💻 Local Development (1 failed)

astro-stable-node (1 failed):

  • createHook({ experimental_force: true }) a run can take over its own earlier hook

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

  • a run can take over its own earlier hook (sveltekit · local-dev / local / node / stable)
  • health check (CLI) - workflow health command reports healthy endpoints (nextjs-webpack · local-dev / local / node / stable)
  • startFromWorkflow - calling start() directly inside a workflow function with hook communication (nuxt · local-dev / local / quickjs / stable)

🛠 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.

  • run-pickup-stall · runs app-generated source against a registered step (tanstack-start) · at 20:45:32Z · abandoned wrun_01M3Z5TE5J52KNTE381FMYWS5G
  • cold-start-warmup · suite warmup (tanstack-start) · at 20:45:39Z · abandoned wrun_01M3Z5TE5QTRJR4G514RD7M9EN
  • run-pickup-stall · 'hookGetConflictWithParallelStepWorkfl…' - hook.getConflict() does not block step execution (nuxt) · at 20:46:32Z · abandoned wrun_01M3Z5W8VJHYSK0KM34ZE800KZ
  • run-pickup-stall · hookCleanupTestWorkflow - hook token reuse after workflow completion (nextjs-webpack) · at 20:51:24Z · abandoned wrun_01M3Z655XWF7NXETQGC0QK0AV8

E2E Test Summary

Summary
Passed Failed Skipped Total
✅ ▲ Vercel Production 3904 0 1253 5157
❌ 💻 Local Development 4987 1 551 5539
✅ 📦 Local Production 4988 0 551 5539
✅ 🐘 Local Postgres 4988 0 551 5539
✅ 🪟 Windows 342 0 40 382
✅ 🌐 Cross-language Conformance 68 0 84 152
✅ dynamic-runs 0 0 0 0
✅ vercel-http-transport 879 0 267 1146
✅ vercel-multi-region 27 0 0 27
✅ vercel-ws-transport 595 0 169 764
Total 20778 1 3466 24245
Details by Category

✅ ▲ Vercel Production

App Passed Failed Skipped
✅ astro-node 142 0 49
✅ astro-quickjs 142 0 49
✅ example-node 142 0 49
✅ example-quickjs 142 0 49
✅ express-node 142 0 49
✅ express-quickjs 142 0 49
✅ fastify-node 142 0 49
✅ fastify-quickjs 142 0 49
✅ hono-node 142 0 49
✅ hono-quickjs 142 0 49
✅ nest-node 142 0 49
✅ nest-quickjs 142 0 49
✅ nextjs-turbopack-node 169 0 22
✅ nextjs-turbopack-quickjs 169 0 22
✅ nextjs-webpack-node 169 0 22
✅ nextjs-webpack-quickjs 169 0 22
✅ nitro-node 142 0 49
✅ nitro-quickjs 142 0 49
✅ nuxt-node 142 0 49
✅ nuxt-quickjs 142 0 49
✅ python-node 66 0 125
✅ sveltekit-node 161 0 30
✅ sveltekit-quickjs 161 0 30
✅ tanstack-start-node 142 0 49
✅ tanstack-start-quickjs 142 0 49
✅ vite-node 142 0 49
✅ vite-quickjs 142 0 49

❌ 💻 Local Development

App Passed Failed Skipped
❌ astro-stable-node 161 1 29
✅ astro-stable-quickjs 162 0 29
✅ express-stable-node 162 0 29
✅ express-stable-quickjs 162 0 29
✅ fastify-stable-node 162 0 29
✅ fastify-stable-quickjs 162 0 29
✅ hono-stable-node 162 0 29
✅ hono-stable-quickjs 162 0 29
✅ nest-stable-node 162 0 29
✅ nest-stable-quickjs 162 0 29
✅ nextjs-turbopack-canary-node 190 0 1
✅ nextjs-turbopack-canary-quickjs 190 0 1
✅ nextjs-turbopack-quickjs-snapshot 190 0 1
✅ nextjs-turbopack-stable-node 190 0 1
✅ nextjs-turbopack-stable-quickjs 190 0 1
✅ nextjs-webpack-canary-node 190 0 1
✅ nextjs-webpack-canary-quickjs 190 0 1
✅ nextjs-webpack-stable-node 190 0 1
✅ nextjs-webpack-stable-quickjs 190 0 1
✅ nitro-stable-node 162 0 29
✅ nitro-stable-quickjs 162 0 29
✅ nuxt-stable-node 162 0 29
✅ nuxt-stable-quickjs 162 0 29
✅ sveltekit-stable-node 181 0 10
✅ sveltekit-stable-quickjs 181 0 10
✅ tanstack-start-node 162 0 29
✅ tanstack-start-quickjs 162 0 29
✅ vite-stable-node 162 0 29
✅ vite-stable-quickjs 162 0 29

✅ 📦 Local Production

App Passed Failed Skipped
✅ astro-stable-node 162 0 29
✅ astro-stable-quickjs 162 0 29
✅ express-stable-node 162 0 29
✅ express-stable-quickjs 162 0 29
✅ fastify-stable-node 162 0 29
✅ fastify-stable-quickjs 162 0 29
✅ hono-stable-node 162 0 29
✅ hono-stable-quickjs 162 0 29
✅ nest-stable-node 162 0 29
✅ nest-stable-quickjs 162 0 29
✅ nextjs-turbopack-canary-node 190 0 1
✅ nextjs-turbopack-canary-quickjs 190 0 1
✅ nextjs-turbopack-quickjs-snapshot 190 0 1
✅ nextjs-turbopack-stable-node 190 0 1
✅ nextjs-turbopack-stable-quickjs 190 0 1
✅ nextjs-webpack-canary-node 190 0 1
✅ nextjs-webpack-canary-quickjs 190 0 1
✅ nextjs-webpack-stable-node 190 0 1
✅ nextjs-webpack-stable-quickjs 190 0 1
✅ nitro-stable-node 162 0 29
✅ nitro-stable-quickjs 162 0 29
✅ nuxt-stable-node 162 0 29
✅ nuxt-stable-quickjs 162 0 29
✅ sveltekit-stable-node 181 0 10
✅ sveltekit-stable-quickjs 181 0 10
✅ tanstack-start-node 162 0 29
✅ tanstack-start-quickjs 162 0 29
✅ vite-stable-node 162 0 29
✅ vite-stable-quickjs 162 0 29

✅ 🐘 Local Postgres

App Passed Failed Skipped
✅ astro-stable-node 162 0 29
✅ astro-stable-quickjs 162 0 29
✅ express-stable-node 162 0 29
✅ express-stable-quickjs 162 0 29
✅ fastify-stable-node 162 0 29
✅ fastify-stable-quickjs 162 0 29
✅ hono-stable-node 162 0 29
✅ hono-stable-quickjs 162 0 29
✅ nest-stable-node 162 0 29
✅ nest-stable-quickjs 162 0 29
✅ nextjs-turbopack-canary-node 190 0 1
✅ nextjs-turbopack-canary-quickjs 190 0 1
✅ nextjs-turbopack-quickjs-snapshot 190 0 1
✅ nextjs-turbopack-stable-node 190 0 1
✅ nextjs-turbopack-stable-quickjs 190 0 1
✅ nextjs-webpack-canary-node 190 0 1
✅ nextjs-webpack-canary-quickjs 190 0 1
✅ nextjs-webpack-stable-node 190 0 1
✅ nextjs-webpack-stable-quickjs 190 0 1
✅ nitro-stable-node 162 0 29
✅ nitro-stable-quickjs 162 0 29
✅ nuxt-stable-node 162 0 29
✅ nuxt-stable-quickjs 162 0 29
✅ sveltekit-stable-node 181 0 10
✅ sveltekit-stable-quickjs 181 0 10
✅ tanstack-start-node 162 0 29
✅ tanstack-start-quickjs 162 0 29
✅ vite-stable-node 162 0 29
✅ vite-stable-quickjs 162 0 29

✅ 🪟 Windows

App Passed Failed Skipped
✅ nextjs-turbopack-node 171 0 20
✅ nextjs-turbopack-quickjs 171 0 20

✅ 🌐 Cross-language Conformance

App Passed Failed Skipped
✅ python 68 0 84

✅ dynamic-runs

App Passed Failed Skipped
✅ astro-vercel 0 0 0
✅ example-vercel 0 0 0
✅ express-vercel 0 0 0
✅ fastify-vercel 0 0 0
✅ hono-vercel 0 0 0
✅ nest-vercel 0 0 0
✅ nextjs-turbopack-vercel 0 0 0
✅ nextjs-webpack-vercel 0 0 0
✅ nitro-vercel 0 0 0
✅ nuxt-vercel 0 0 0
✅ sveltekit-vercel 0 0 0
✅ tanstack-start-vercel 0 0 0
✅ vite-vercel 0 0 0

✅ vercel-http-transport

App Passed Failed Skipped
✅ example 142 0 49
✅ express 142 0 49
✅ hono 142 0 49
✅ nextjs-turbopack 169 0 22
✅ nitro 142 0 49
✅ vite 142 0 49

✅ vercel-multi-region

App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0

✅ vercel-ws-transport

App Passed Failed Skipped
✅ example 142 0 49
✅ express 142 0 49
✅ nextjs-turbopack 169 0 22
✅ vite 142 0 49

📋 View full workflow run

@github-actions

github-actions Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Sim World

Simulated world deterministic testing for races. Traces

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

fence=per-spec

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

Full trace: world-sim.txt

@github-actions

github-actions Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor
Framework Flow route Step reg. Framework output
hono 267.6 KiB (+435 B) 101.5 KiB (+4.2 KiB) 2.01 MiB (+8.8 KiB)
nextjs-turbopack 275.0 KiB (+420 B) 426 B (±0) 990.0 KiB (+3.8 KiB)
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.

9bc079b · run

@alangenfeld
alangenfeld force-pushed the alangenfeld/workflow-dynamic-workflows-cookbook branch from ac77874 to f45166a Compare October 1, 2026 01:27
@alangenfeld
alangenfeld force-pushed the alangenfeld/workflow-dynamic-workflows-cookbook branch from f45166a to dc9bc84 Compare October 1, 2026 16:21
@alangenfeld
alangenfeld force-pushed the alangenfeld/workflow-dynamic-workflows-cookbook branch from 4c1f9e6 to 8741a51 Compare October 1, 2026 18:00
@vercel
vercel Bot temporarily deployed to Preview – workflow-docs October 1, 2026 19:53 Inactive
alangenfeld added a commit that referenced this pull request Oct 2, 2026
## Summary & Motivation

Fills gaps the 5.0.0 dogfood surfaced on the dynamic workflows concept
page: a table of the per-gate refusals and which of them are fatal, how
a Vercel project gets dynamic-source storage, what the 2,048-byte
execution-context budget actually buys, that the workflow ID hashes raw
source bytes, and that "trusted" means reviewed application code rather
than anything a model did not write.

Stacked on #4541, which adds the cookbook recipe this page now links to.

## Test Plan

Docs only. Links, anchors, quoted error messages, and the
fatal/retryable behavior were checked by hand against the runtime source
on main.

#4534 (open) edits this page's `exportName` rule. This PR leaves that
line alone, quotes only the stable prefix of the execution-context error
that #4534 extends, and does not document #4534's validation messages.

## Docs Preview

| Page | Link |
| --- | --- |
| Dynamic workflows |
[/docs/advanced/dynamic-workflows](https://workflow-docs-rakhde7hj.vercel.sh/docs/advanced/dynamic-workflows)
|
| Errors for each gate |
[#errors-for-each-gate](https://workflow-docs-rakhde7hj.vercel.sh/docs/advanced/dynamic-workflows#errors-for-each-gate)
|
| Enabling storage on Vercel |
[#enabling-storage-on-vercel](https://workflow-docs-rakhde7hj.vercel.sh/docs/advanced/dynamic-workflows#enabling-storage-on-vercel)
|

---------

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
…fter deploy

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
… proves

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
…v1 contract

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
… reject invalid parent links

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
## Summary & Motivation

Fills gaps the 5.0.0 dogfood surfaced on the dynamic workflows concept
page: a table of the per-gate refusals and which of them are fatal, how
a Vercel project gets dynamic-source storage, what the 2,048-byte
execution-context budget actually buys, that the workflow ID hashes raw
source bytes, and that "trusted" means reviewed application code rather
than anything a model did not write.

Stacked on #4541, which adds the cookbook recipe this page now links to.

## Test Plan

Docs only. Links, anchors, quoted error messages, and the
fatal/retryable behavior were checked by hand against the runtime source
on main.

#4534 (open) edits this page's `exportName` rule. This PR leaves that
line alone, quotes only the stable prefix of the execution-context error
that #4534 extends, and does not document #4534's validation messages.

## Docs Preview

| Page | Link |
| --- | --- |
| Dynamic workflows |
[/docs/advanced/dynamic-workflows](https://workflow-docs-rakhde7hj.vercel.sh/docs/advanced/dynamic-workflows)
|
| Errors for each gate |
[#errors-for-each-gate](https://workflow-docs-rakhde7hj.vercel.sh/docs/advanced/dynamic-workflows#errors-for-each-gate)
|
| Enabling storage on Vercel |
[#enabling-storage-on-vercel](https://workflow-docs-rakhde7hj.vercel.sh/docs/advanced/dynamic-workflows#enabling-storage-on-vercel)
|

---------

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>

This branch was successfully deployed

1 active deployment
Preview – workflow-docs — 9bc079b9 Deployed Oct 2, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant