Skip to content

[world-postgres] Don't move an ended run back to running on a late run_started - #5136

Merged
alangenfeld merged 2 commits into
mainfrom
alangenfeld/pg-run-started-terminal-guard
Oct 29, 2026
Merged

alangenfeld merged 2 commits into
mainfrom
alangenfeld/pg-run-started-terminal-guard

Conversation

@alangenfeld

@alangenfeld alangenfeld commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Summary & Motivation

A run_started that arrives just as the run ends used to set the run back to running. The row was left with its output and completion time still set, and reading the run then failed. Now the late run_started leaves the ended run alone and is refused, the same answer it would have gotten had the run already ended when it was checked.

  • The UPDATE that marks the run running now skips runs in a terminal status. If it matches nothing because the run has ended, the event fails with RunExpiredError and no run_started is written.

This showed up as ZodError failures from runs.get in the world-postgres e2e lanes, in the start({ hook }) "start or resume" test: https://github.com/vercel/workflow/actions/runs/40935700151

Test Plan

Added a test that reproduces the race every time. A second connection ends the run and holds its row lock while run_started waits on that lock. Against a local Postgres 17 the test fails without the fix (the run comes back running) and passes with it. The world-postgres storage and spec tests pass locally.

…n_started

run_started's UPDATE was unguarded, so a run that ended between the
validation read and the UPDATE was set back to running, leaving a row with
a completion and a live status that runs.get then fails to parse. The
UPDATE now excludes terminal runs and the event is refused with
RunExpiredError, matching the pre-validation answer.

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

changeset-bot Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: fe4a659

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

This PR includes changesets to release 1 package
Name Type
@workflow/world-postgres 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 Oct 29, 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 29, 2026 7:20pm UTC
example-nextjs-workflow-webpack Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
example-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-astro-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-express-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-fastify-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-hono-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-nestjs-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-nitro-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-nuxt-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-python-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-sveltekit-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-tanstack-start-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workbench-vite-workflow Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workflow-swc-playground Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workflow-tarballs Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
workflow-web Ready Ready Preview, v0 Oct 29, 2026 7:20pm UTC
1 Skipped Deployment
Project Deployment Actions Updated
workflow-docs Skipped Skipped v0 Oct 29, 2026 7:20pm UTC

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit fe4a659 · Thu, 29 Oct 2026 19:33:47 GMT · run logs

Backend: vercel · app: nextjs-turbopack

Metric Scenario Best (ms) P75 (ms) P90 (ms) P99 (ms) Samples
TTFS step 351 (-71%) 💚 2044 🔴 (+26%) 🔻 2141 🔴 (+27%) 🔻 2739 🔴 (+16%) 🔻 30
TTFS stream 338 (-4.8%) 1939 🔴 (+26%) 🔻 2027 🔴 (+30%) 🔻 2431 🔴 (+48%) 🔻 30
TTFS hook + stream 500 (-65%) 💚 2273 🔴 (+21%) 🔻 2334 🔴 (+21%) 🔻 2485 🔴 (+23%) 🔻 30
Fan-out TTFS Promise.all(100 steps) 621 (±0%) 839 (+2.6%) 1102 (-43%) 💚 2375 (+3.0%) 10
Fan-out TTLS Promise.all(100 steps) 1655 (+4.5%) 4436 (+3.0%) 4818 (+12%) 5259 (-20%) 💚 10
STSO 1020 steps (inline) 115 (+31%) 🔻 140 (+12%) 157 (+6.1%) 213 (-10%) 1019
WO 1020 steps 138919 (+14%) 138919 (+14%) 138919 (+14%) 138919 (+14%) 1
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 121252ms → this run 138616ms (Δ +17364ms, +14%)

 50-100 ms  ┃███                      main 137  this   0  -137
100-150 ms  ██████████████████████░┃  main 790  this 860   +70
150-200 ms  ██░┃                      main  73  this 135   +62
200-250 ms  ┃                         main   9  this  19   +10
250-300 ms  ┃                         main   3  this   1    -2
300-350 ms  ┃                         main   1  this   2    +1
350-400 ms  ┃                         main   3  this   2    -1
400-450 ms  ┃                         main   1  this   0    -1
450-500 ms  ┃                         main   2  this   0    -2
ℹ️ Metric definitions & methodology

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.

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)

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

🔴 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. Streaming delivery performance is measured in durabench.

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

@github-actions

github-actions Bot commented Oct 29, 2026 •

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.

  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep (python · vercel-prod / vercel / node / production)

🛠 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 19:22:32Z · abandoned wrun_01M64HSW9YNV4BZPGE3RCQW80Q
  • cold-start-warmup · suite warmup (tanstack-start) · at 19:22:36Z · abandoned wrun_01M64HSWAAG3Y27P248NY2SS57
  • run-pickup-stall · stepFunctionAsStartArgWorkflow - step function reference passed as start() argument (nextjs-webpack) · at 19:27:31Z · abandoned wrun_01M64J30BGPP1MPST5FWG9HQWH
  • run-pickup-stall · cancelRun - cancelling a running workflow (nextjs-webpack) · at 19:27:32Z · abandoned wrun_01M64J317CJFH91WXKHAEE17AF

E2E Test Summary

Summary
Passed Failed Skipped Total
✅ ▲ Vercel Production 3982 0 878 4860
✅ 💻 Local Development 4669 0 551 5220
✅ 📦 Local Production 4669 0 551 5220
✅ 🐘 Local Postgres 4669 0 551 5220
✅ 🪟 Windows 348 0 12 360
✅ 🌐 Cross-language Conformance 68 0 87 155
✅ dynamic-runs 0 0 0 0
✅ vercel-http-transport 897 0 183 1080
✅ vercel-multi-region 27 0 0 27
✅ vercel-ws-transport 607 0 113 720
Total 19936 0 2926 22862
Details by Category

✅ ▲ Vercel Production

App Passed Failed Skipped
✅ astro-node 145 0 35
✅ astro-quickjs 145 0 35
✅ example-node 145 0 35
✅ example-quickjs 145 0 35
✅ express-node 145 0 35
✅ express-quickjs 145 0 35
✅ fastify-node 145 0 35
✅ fastify-quickjs 145 0 35
✅ hono-node 145 0 35
✅ hono-quickjs 145 0 35
✅ nest-node 145 0 35
✅ nest-quickjs 145 0 35
✅ nextjs-turbopack-node 172 0 8
✅ nextjs-turbopack-quickjs 172 0 8
✅ nextjs-webpack-node 172 0 8
✅ nextjs-webpack-quickjs 172 0 8
✅ nitro-node 145 0 35
✅ nitro-quickjs 145 0 35
✅ nuxt-node 145 0 35
✅ nuxt-quickjs 145 0 35
✅ python-node 66 0 114
✅ sveltekit-node 164 0 16
✅ sveltekit-quickjs 164 0 16
✅ tanstack-start-node 145 0 35
✅ tanstack-start-quickjs 145 0 35
✅ vite-node 145 0 35
✅ vite-quickjs 145 0 35

✅ 💻 Local Development

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

✅ 📦 Local Production

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

✅ 🐘 Local Postgres

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

✅ 🪟 Windows

App Passed Failed Skipped
✅ nextjs-turbopack-node 174 0 6
✅ nextjs-turbopack-quickjs 174 0 6

✅ 🌐 Cross-language Conformance

App Passed Failed Skipped
✅ python 68 0 87

✅ 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 145 0 35
✅ express 145 0 35
✅ hono 145 0 35
✅ nextjs-turbopack 172 0 8
✅ nitro 145 0 35
✅ vite 145 0 35

✅ vercel-multi-region

App Passed Failed Skipped
✅ nextjs-turbopack 27 0 0

✅ vercel-ws-transport

App Passed Failed Skipped
✅ example 145 0 35
✅ express 145 0 35
✅ nextjs-turbopack 172 0 8
✅ vite 145 0 35

📋 View full workflow run

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Sim World

Simulated world deterministic testing for races. Traces

🟢 world-sim scenario book — 0 fail of 44 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 11 0ms ok 0
✅ hook-at-step-completed completed 11 0ms ok 0
✅ hook-at-hook-created completed 11 0ms ok 0
✅ claim-hook-at-registration completed 11 0ms ok 0
✅ claim-hook-at-step-started completed 11 0ms ok 0
✅ deadline-hook-wins completed 6 1.0h ok 0
✅ deadline-expires completed 6 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 11 0ms ok 0
✅ peek-hook-before-branch completed 11 0ms ok 0
✅ peek-hook-after-branch completed 11 0ms ok 0
✅ peek-hook-at-registration completed 11 0ms ok 0
✅ race-hook-before-probe completed 11 0ms ok 0
✅ race-hook-after-probe completed 11 0ms ok 0
✅ race-duplicate-delivery completed 12 0ms ok 0
✅ attr-hook-before-step completed 10 0ms ok 0
✅ attr-hook-after-step completed 10 0ms ok 0
✅ attr-from-step-body completed 12 0ms ok 0
✅ fork-hook-after-timeout completed 13 1.0m ok 0
✅ fork-hook-before-timeout completed 13 1.0m ok 0
✅ count-hook-after-timeout completed 16 1.0m ok 0
✅ count-hook-before-timeout completed 19 1.0m ok 0
✅ stale-read-step-count-fork completed 19 1.0m ok 0
✅ stale-read-equal-step-counts completed 13 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 16 1.0m ok 0
✅ in-flight-before-decision-counted completed 16 1.0m ok 0
✅ in-flight-after-decision completed 18 2.0m ok 0
✅ stale-read-step-count-fork-fenced completed 19 1.0m ok 0
✅ fork-hook-wins completed 12 1.0m ok 0
✅ fork-timeout-wins completed 12 1.0m ok 0
✅ unclaimed-payload-under-fork completed 16 1.0m ok 0
✅ claimed-payload-under-fork completed 16 1.0m ok 0
✅ writers-independent-step-bodies completed 12 0ms ok 0
✅ writers-scripted-tempo completed 11 0ms ok 0
✅ cancel-mid-step cancelled 7 0ms skipped 0

Full trace: world-sim.txt

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor
Framework Flow route Step reg. Framework output
hono 267.6 KiB (±0) 95.7 KiB (±0) 2.01 MiB (±0)
nextjs-turbopack 275.1 KiB (±0) 426 B (±0) 977.0 KiB (±0)
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.

fe4a659 · run

…rked on the row

The test polled for any ungranted lock and committed when its deadline
passed even without one, and then the validation read refuses the
run_started on its own. It now waits for this run_started's UPDATE to be
waiting on a lock before ending the run.

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
@vercel
vercel Bot temporarily deployed to Preview – workflow-docs October 29, 2026 19:18 Inactive
@alangenfeld
alangenfeld marked this pull request as ready for review October 29, 2026 19:24
@alangenfeld
alangenfeld requested a review from a team as a code owner October 29, 2026 19:24
@alangenfeld
alangenfeld merged commit 62c8a23 into main Oct 29, 2026
188 checks passed
@alangenfeld
alangenfeld deleted the alangenfeld/pg-run-started-terminal-guard branch October 29, 2026 19:34
@github-actions github-actions Bot mentioned this pull request Oct 29, 2026
github-actions Bot added a commit that referenced this pull request Oct 29, 2026
…n_started (#5136)

A `run_started` that arrives just as the run ends used to set the run
back to running. The row was left with its output and completion time
still set, and reading the run then failed. Now the late `run_started`
leaves the ended run alone and is refused, the same answer it would have
gotten had the run already ended when it was checked.

- The UPDATE that marks the run running now skips runs in a terminal
status. If it matches nothing because the run has ended, the event fails
with `RunExpiredError` and no `run_started` is written.

This showed up as `ZodError` failures from `runs.get` in the
world-postgres e2e lanes, in the `start({ hook })` "start or resume"
test: https://github.com/vercel/workflow/actions/runs/40935700151

Added a test that reproduces the race every time. A second connection
ends the run and holds its row lock while `run_started` waits on that
lock. Against a local Postgres 17 the test fails without the fix (the
run comes back `running`) and passes with it. The world-postgres storage
and spec tests pass locally.

---------

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

Copy link
Copy Markdown
Contributor

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

VaguelySerious added a commit that referenced this pull request Oct 31, 2026
…ing on a late run_started (#5138)

Automated backport of #5136 to `stable` ([backport job
run](https://github.com/vercel/workflow/actions/runs/40941356751)).

Signed-off-by: Alex Langenfeld <alex.langenfeld@vercel.com>
Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Co-authored-by: Peter Wielander <peter.wielander@vercel.com>
@github-actions github-actions Bot mentioned this pull request Oct 31, 2026
pranaygp pushed a commit that referenced this pull request Nov 4, 2026
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to stable, this PR
will be updated.


# Releases
## @workflow/world-postgres@4.4.0

### Minor Changes

- [#4759](#4759)
[`3ff458e`](3ff458e)
Thanks [@pranaygp](https://github.com/pranaygp)! - Add
`jobLockStaleSeconds` (`WORKFLOW_POSTGRES_JOB_LOCK_STALE_SECONDS`,
default `0`, off). When set, a running delivery renews its Graphile job
lock, and a job whose process died is redelivered by another process
once its lock has gone unrenewed for that many seconds, instead of after
Graphile Worker's fixed 4 hours or the next restart. `30` is a good
value when more than one process shares the database. It's off by
default because of rolling upgrades: processes on an earlier version
don't renew their locks, so turn it on once every process that shares
the database runs this version.

### Patch Changes

- [#5136](#5136)
[`5c9b65d`](5c9b65d)
Thanks [@alangenfeld](https://github.com/alangenfeld)! - A `run_started`
that races the run ending no longer moves the run back to `running`;
it's refused with `RunExpiredError`.

- Updated dependencies
[[`ceaaa5c`](ceaaa5c),
[`b065b0b`](b065b0b)]:
  - @workflow/world-local@4.4.5
## @workflow/astro@4.0.31

### Patch Changes

- Updated dependencies
[[`e4dbc29`](e4dbc29)]:
  - @workflow/builders@4.1.21
  - @workflow/rollup@4.0.31
  - @workflow/vite@4.0.31
## @workflow/builders@4.1.21

### Patch Changes

- [#5063](#5063)
[`e4dbc29`](e4dbc29)
Thanks [@joelfickson](https://github.com/joelfickson)! - Export
`workflowSerdeComputedPropertyPattern` alongside the other workflow
pattern regexes.

- Updated dependencies []:
  - @workflow/core@4.8.16
## @workflow/cli@4.3.20

### Patch Changes

- [#5182](#5182)
[`f3d6142`](f3d6142)
Thanks [@VaguelySerious](https://github.com/VaguelySerious)! - Respect
`--project` and `--team` over the inferred `.vercel` link, and prefer
the nearest `.vercel/project.json` in monorepos

- Updated dependencies
[[`e4dbc29`](e4dbc29),
[`dbfd1ba`](dbfd1ba),
[`ceaaa5c`](ceaaa5c),
[`b065b0b`](b065b0b)]:
  - @workflow/builders@4.1.21
  - @workflow/web@4.1.32
  - @workflow/world-local@4.4.5
  - @workflow/core@4.8.16
## @workflow/core@4.8.16

### Patch Changes

- Updated dependencies
[[`ceaaa5c`](ceaaa5c),
[`b065b0b`](b065b0b)]:
  - @workflow/world-local@4.4.5
## @workflow/nest@4.0.32

### Patch Changes

- Updated dependencies
[[`e4dbc29`](e4dbc29)]:
  - @workflow/builders@4.1.21
## @workflow/next@4.1.20

### Patch Changes

- [#5063](#5063)
[`e4dbc29`](e4dbc29)
Thanks [@joelfickson](https://github.com/joelfickson)! - Run the
Turbopack workflow loader on files that use `static
[WORKFLOW_SERIALIZE]` computed keys (such as `@ai-sdk/openai` models),
fixing "Class … not found" errors in steps.

- Updated dependencies
[[`e4dbc29`](e4dbc29)]:
  - @workflow/builders@4.1.21
  - @workflow/core@4.8.16
## @workflow/nitro@4.1.22

### Patch Changes

- Updated dependencies
[[`e4dbc29`](e4dbc29),
[`dbfd1ba`](dbfd1ba)]:
  - @workflow/builders@4.1.21
  - @workflow/web@4.1.32
  - @workflow/rollup@4.0.31
  - @workflow/vite@4.0.31
  - @workflow/core@4.8.16
## @workflow/nuxt@4.0.32

### Patch Changes

- [#5211](#5211)
[`d30f07e`](d30f07e)
Thanks [@atinux](https://github.com/atinux)! - Upgrade `@nuxt/kit` to
4.6.3 to pick up the fix for CVE-2026-71314.

- Updated dependencies []:
  - @workflow/nitro@4.1.22
## @workflow/rollup@4.0.31

### Patch Changes

- Updated dependencies
[[`e4dbc29`](e4dbc29)]:
  - @workflow/builders@4.1.21
## @workflow/sveltekit@4.0.31

### Patch Changes

- Updated dependencies
[[`e4dbc29`](e4dbc29)]:
  - @workflow/builders@4.1.21
  - @workflow/rollup@4.0.31
  - @workflow/vite@4.0.31
## @workflow/vite@4.0.31

### Patch Changes

- Updated dependencies
[[`e4dbc29`](e4dbc29)]:
  - @workflow/builders@4.1.21
## @workflow/vitest@4.0.32

### Patch Changes

- Updated dependencies
[[`e4dbc29`](e4dbc29),
[`ceaaa5c`](ceaaa5c),
[`b065b0b`](b065b0b)]:
  - @workflow/builders@4.1.21
  - @workflow/world-local@4.4.5
  - @workflow/rollup@4.0.31
  - @workflow/core@4.8.16
## @workflow/web@4.1.32

### Patch Changes

- [#5079](#5079)
[`dbfd1ba`](dbfd1ba)
Thanks [@karthikscale3](https://github.com/karthikscale3)! - Recognize
unframed serialized abort packets in the Streams viewer so encrypted
packets can be decrypted.
## @workflow/web-shared@4.1.32

### Patch Changes

- Updated dependencies []:
  - @workflow/core@4.8.16
## workflow@4.8.16

### Patch Changes

- Updated dependencies
[[`f3d6142`](f3d6142),
[`d30f07e`](d30f07e),
[`e4dbc29`](e4dbc29)]:
  - @workflow/cli@4.3.20
  - @workflow/nuxt@4.0.32
  - @workflow/next@4.1.20
  - @workflow/astro@4.0.31
  - @workflow/nest@4.0.32
  - @workflow/nitro@4.1.22
  - @workflow/rollup@4.0.31
  - @workflow/sveltekit@4.0.31
  - @workflow/core@4.8.16
  - @workflow/typescript-plugin@4.0.3
## @workflow/world-local@4.4.5

### Patch Changes

- [#5069](#5069)
[`ceaaa5c`](ceaaa5c)
Thanks [@AndrewBarba](https://github.com/AndrewBarba)! - Deliver stream
chunks in the order they were written. A reader that opened, or polled,
while chunks were being written could get a later chunk before an
earlier one, and could get a chunk twice. Writes to one stream now land
in order, including a `writeToStreamMulti` group and concurrent writes,
and the reader holds live chunks while it reads from disk.

- [#4909](#4909)
[`b065b0b`](b065b0b)
Thanks [@fazxes](https://github.com/fazxes)! - Name each stream chunk as
it lands, after every chunk already in the stream, so a write that
stalled before landing no longer lands ahead of chunks a reader already
read.
## @workflow/world-testing@4.1.31

### Patch Changes

- Updated dependencies
[[`f3d6142`](f3d6142)]:
  - @workflow/cli@4.3.20
  - workflow@4.8.16
  - @workflow/core@4.8.16

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

This branch was previously deployed

1 inactive deployment
Preview – workflow-docs — fe4a6593 Deployed Oct 29, 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.

2 participants