Skip to content

feat(core): step inputs - reconstruct selected arguments through replay - #4239

Open
AndrewBarba wants to merge 3 commits into
mainfrom
barba/replay-derived-step-inputs
Open

feat(core): step inputs - reconstruct selected arguments through replay#4239
AndrewBarba wants to merge 3 commits into
mainfrom
barba/replay-derived-step-inputs

Conversation

@AndrewBarba

@AndrewBarba AndrewBarba commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Description

Closes #4238. An accumulating-state loop persists the same history in every step input, producing quadratic input storage even when each step returns a small delta. turnStep.replayInputs = [0] lets the workflow reconstruct selected plain-data arguments while keeping ordinary arguments, closures, and receivers persisted.

Both Node and QuickJS capture selected values at invocation time. Durable inputs contain a versioned envelope, SHA-256 fingerprints, and an inspection label. Queued execution and retries replay to the invocation, verify the captures, and combine them with the recorded ordinary arguments before using the existing executor. Queue messages carry only a routing flag for reconstruction. Existing input records remain readable; completed results still replay without execution.

This is an opt-in input-storage feature. It adds no state store, World retrieval API, automatic diffing, or checkpoints. Applications continue to own output deltas. Cold attempts pay for workflow replay and fingerprinting. The documentation covers supported values, binding, isolation, inspection, and that tradeoff.

Documentation preview

How did you test your changes?

  • Refreshed dependencies and built @workflow/core and its prerequisites, resolving the stale StreamError export baseline.
  • Core package suite: 2,602 passed; World: 204 passed; builders: 253 passed. The subsequent focused recovery suite passes all 30 cases across both engines.
  • Recovery coverage includes queued overflow in a fresh VM, an interrupted inline owner and queued attempt, delayed/early retries, attempt limits, recorded-output replay, concurrent wakes, cancellation, bound arguments, captured closures, mixed serializers, invocation-time mutation, proxy rejection, and fingerprint mismatches.
  • Actual serialization asserts omitted state is absent from stored inputs and queue messages. Compiler tests verify the property survives both SWC transforms and minification.
  • TypeScript check, changed documentation samples, Biome, changeset validation, and test-discovery guard pass. Biome reports advisory warnings. A broader local build that included the SWC package stopped because Rust is unavailable; the core dependency build and existing WASM compiler tests pass.

CI also exposed timing sensitivity in the unchanged Windows run-return-value-real-world.test.ts suite (800 ms assertions). The new recovery tests passed on every Windows attempt; the unit job passed on rerun. DCO and the required end-to-end aggregate are green.

The fixed-size delta benchmark verifies identical results and execution counts. Bytes below count persisted step inputs and outputs, without compression:

Steps Replay-derived inputs Full snapshot inputs
8 3,944 9,837
16 7,888 36,413
32 15,776 139,869

PR Checklist - Required to merge

  • Changeset added for @workflow/core and @workflow/world.
  • Commit is cryptographically signed and includes DCO sign-off.
  • Required CI checks pass.

@changeset-bot

changeset-bot Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 52e0d44

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

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

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercel Bot commented Sep 18, 2026 •
edited
Loading

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 Sep 18, 2026 2:14am UTC
example-nextjs-workflow-webpack Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
example-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-astro-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-express-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-fastify-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-hono-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-nestjs-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-nitro-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-nuxt-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-python-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-sveltekit-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-tanstack-start-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workbench-vite-workflow Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workflow-docs Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workflow-swc-playground Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workflow-tarballs Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC
workflow-web Ready Ready Preview, v0 Sep 18, 2026 2:14am UTC

@github-actions

github-actions Bot commented Sep 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 52e0d44 · Fri, 18 Sep 2026 02:38:07 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 2136 (+29%) 🔻 2289 🔴 (+16%) 🔻 2346 🔴 (+17%) 🔻 2465 🔴 (+3.4%) 30
TTFS stream 276 (+79%) 🔻 2335 🔴 (+25%) 🔻 2350 🔴 (+22%) 🔻 2393 🔴 (+20%) 🔻 30
TTFS hook + stream 2315 (+42%) 🔻 2633 🔴 (+16%) 🔻 2703 🔴 (+14%) 3063 🔴 (+11%) 30
Fan-out TTFS Promise.all(100 steps) 470 (+11%) 861 (+54%) 🔻 898 (+54%) 🔻 3044 (+36%) 🔻 10
Fan-out TTLS Promise.all(100 steps) 2081 (+50%) 🔻 3634 (-13%) 5527 (+4.7%) 10657 (+28%) 🔻 10
STSO 1020 steps (inline) 123 (+24%) 🔻 163 (+13%) 182 (+12%) 245 (-2.8%) 1019
WO 1020 steps 162275 (+11%) 162275 (+11%) 162275 (+11%) 162275 (+11%) 1
CRTT first chunk (pooled) 73 (+24%) 🔻 130 (+23%) 🔻 159 (-11%) 224 (-30%) 💚 28

Streams

Scenario CRTT 1st p75 p90 p99 CDV max iters
paced control (100/s, 60B) 123 (+23%) 254 (+37%) 451 (+71%) 652 (+16%) 193 (+28%) 10
size sweep (100/s, 160B-12KB) 99.5 (+5%) 252 (+27%) 338 (-14%) 1022 (+71%) 196 (-23%) 10
replay gateway-gpt-5.4-nano-2000t (1x) 93 (-4%) 200 (+25%) 260 (+11%) 452 (-53%) 335 (-9%) 3
replay eve-gpt-5.6-sol-2000t (1x) 122 (+45%) 189 (-5%) 226 (-25%) 433 (-50%) 370 (-25%) 2
replay eve-gpt-5.6-sol-2000t (2x) 113 (+12%) 310 (-26%) 384 (-41%) 596 (-32%) 342 (-26%) 3
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 145702ms → this run 162100ms (Δ +16398ms, +11%)

 50-100 ms  ┃                         main   1  this   0    -1
100-150 ms  ███████████┃████████████  main 811  this 419  -392
150-200 ms  █████░░░░░░░░░░┃          main 175  this 545  +370
200-250 ms  ┃                         main  21  this  46   +25
250-300 ms  ┃                         main   8  this   5    -3
300-350 ms  ┃                         main   1  this   2    +1
350-400 ms  ┃                         main   1  this   1    +0
400-450 ms  ┃                         main   0  this   1    +1
500-550 ms  ┃                         main   1  this   0    -1
📈 CRTT drill-down vs main (RTT distributions & profiles) 
variant  RTT 1ms→5s+             avg         p50         p90          p99     n
control  ······▁█▅▁···  195.9 (+39%)  170 (+36%)  451 (+71%)   652 (+16%)  3000
sweep    ······▁█▄▁▁··    196 (+27%)  165 (+24%)  338 (-14%)  1022 (+71%)  3000
gw 1x    ·····▁▂█▂▁···   150.3 (+3%)  137 (+12%)  260 (+11%)   452 (-53%)  5295
eve 1x   ·····▁▂█▂▁···   155.5 (+2%)  132 (+15%)  226 (-25%)   433 (-50%)  5186
eve 2x   ······▁▇█▁···   228.7 (-8%)  209 (+22%)  384 (-41%)   596 (-32%)  7779

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

control  ▇██▄▅▅▇▄▁▃  172–213ms
sweep    ▂▃▄█▆▅▄▂▁▂  161–248ms
gw 1x    ▃▂█▄▅▂▄▄▃▁  134–177ms
eve 1x   █▂▃▅▅▂▇▇▄▁  133–180ms
eve 2x   ▂▁▂▃▁▂▃█▅▃  185–328ms

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

sweep  ▃█▅▄▃▁▁  194–199ms

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

control  ▅▇▄▅▆█▄▄▄▁  43–72ms
sweep    ▁▄█▅▄▆▃▁▂▂  60–94ms
gw 1x    ▆▆█▁▆▄▅▅▄▆  40–50ms
eve 1x   █▅▃▄▄▄▇▇▁▂  23–35ms
eve 2x   █▆▂▁▃▂▄▁▅▅  26–41ms
ℹ️ 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 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

✅ All tests passed

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

  • health check (CLI) - workflow health command reports healthy endpoints (fastify · local-dev / local / node / 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.

  • cold-start-warmup · suite warmup (tanstack-start) · at 02:17:07Z · abandoned wrun_01M2S4TDE9CN0HT52GXV42N4Q3
  • run-pickup-stall · readableStreamWorkflow (nuxt) · at 02:17:28Z · abandoned wrun_01M2S4VEJ0P4FDEANXDM5GXQ9N
  • run-pickup-stall · plainModuleDoneHook resumed via plain API route (o2flow shape) (nextjs-webpack) · at 02:25:13Z · abandoned wrun_01M2S59MJJ0351M21TG86FXFBS

E2E Test Summary

Summary
Passed Failed Skipped Total
✅ ▲ Vercel Production 3670 0 731 4401
✅ 💻 Local Development 4014 0 550 4564
✅ 📦 Local Production 4014 0 550 4564
✅ 🐘 Local Postgres 4014 0 550 4564
✅ 🪟 Windows 324 0 2 326
✅ 🌐 Cross-language Conformance 68 0 76 144
✅ vercel-http-transport 825 0 153 978
✅ vercel-multi-region 27 0 0 27
✅ vercel-ws-transport 559 0 93 652
Total 17515 0 2705 20220
Details by Category

✅ ▲ Vercel Production

App Passed Failed Skipped
✅ astro-node 133 0 30
✅ astro-quickjs 133 0 30
✅ example-node 133 0 30
✅ example-quickjs 133 0 30
✅ express-node 133 0 30
✅ express-quickjs 133 0 30
✅ fastify-node 133 0 30
✅ fastify-quickjs 133 0 30
✅ hono-node 133 0 30
✅ hono-quickjs 133 0 30
✅ nest-node 133 0 30
✅ nest-quickjs 133 0 30
✅ nextjs-turbopack-node 160 0 3
✅ nextjs-turbopack-quickjs 160 0 3
✅ nextjs-webpack-node 160 0 3
✅ nextjs-webpack-quickjs 160 0 3
✅ nitro-node 133 0 30
✅ nitro-quickjs 133 0 30
✅ nuxt-node 133 0 30
✅ nuxt-quickjs 133 0 30
✅ python-node 66 0 97
✅ sveltekit-node 152 0 11
✅ sveltekit-quickjs 152 0 11
✅ tanstack-start-node 133 0 30
✅ tanstack-start-quickjs 133 0 30
✅ vite-node 133 0 30
✅ vite-quickjs 133 0 30

✅ 💻 Local Development

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

✅ 📦 Local Production

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

✅ 🐘 Local Postgres

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

✅ 🪟 Windows

App Passed Failed Skipped
✅ nextjs-turbopack-node 162 0 1
✅ nextjs-turbopack-quickjs 162 0 1

✅ 🌐 Cross-language Conformance

App Passed Failed Skipped
✅ python 68 0 76

✅ vercel-http-transport

App Passed Failed Skipped
✅ example 133 0 30
✅ express 133 0 30
✅ hono 133 0 30
✅ nextjs-turbopack 160 0 3
✅ nitro 133 0 30
✅ vite 133 0 30

✅ vercel-multi-region

App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0

✅ vercel-ws-transport

App Passed Failed Skipped
✅ example 133 0 30
✅ express 133 0 30
✅ nextjs-turbopack 160 0 3
✅ vite 133 0 30

📋 View full workflow run

@AndrewBarba
fix(core): step inputs - preserve retry backoff across wakes
9867486 
Signed-off-by: Andrew Barba <barba@hey.com>
@github-actions

github-actions Bot commented Sep 18, 2026 •
edited
Loading

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 18, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor
Framework Flow route Step reg. Framework output
hono 251.1 KiB (±0) 93.5 KiB (±0) 1.90 MiB (+3.5 KiB)
nextjs-turbopack 258.5 KiB (±0) 426 B (±0) 904.4 KiB (+1.4 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.

52e0d44 · run

@AndrewBarba
test(core): step inputs - make the retry deadline deterministic
52e0d44 
Signed-off-by: Andrew Barba <barba@hey.com>
@AndrewBarba
AndrewBarba marked this pull request as ready for review September 18, 2026 02:42
@AndrewBarba
AndrewBarba requested a review from a team as a code owner September 18, 2026 02:42
@AndrewBarba AndrewBarba mentioned this pull request Sep 18, 2026
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Support replay-derived step arguments without persisting full inputs

1 participant

@AndrewBarba