[docs] Document WORKFLOW_NODE_HTTP in the v4 World docs - #4050
Merged
Merged
Conversation
The flag ships in @workflow/world-vercel 4.7.0 and is documented only in the v5 docs, so a 4.x user has no way to find it short of reading package source. That is how it was actually found in the field, after nine days of an outage the flag addresses. Adds the entry to the v4 Vercel World page (when to reach for it, the symptom that leads here, and what the swap costs) and a pointer from the v4 Local World page, mirroring how v5 splits it. v4 has no consolidated environment-variable page, so the World pages are the only home for it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
🦋 Changeset detectedLatest commit: bb0bdd1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen 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 |
Contributor
Sim WorldSimulated world deterministic testing for races. Traces 🟠 world-sim scenario book — 1 fail of 41 total
Full trace: |
VaguelySerious
marked this pull request as ready for review
September 9, 2026 14:28
|
|
||
| This exists for deployments where that library is not usable, rather than as a tuning knob. Reach for it when: | ||
|
|
||
| - your bundler mangles the library's internals, so requests through it fail or never settle; |
Contributor
There was a problem hiding this comment.
this option sounds more like an implementation detail the client should'nt have to ideally configure. but fine as a middle ground for now.
karthikscale3
approved these changes
Sep 9, 2026
Contributor
|
No backport to The commit only touches To override, re-run the Backport to stable workflow manually via |
pranaygp
added a commit
that referenced
this pull request
Sep 9, 2026
…c-workflow-source * origin/main: (22 commits) feat(streams): add writer session seam (#3832) docs: document WORKFLOW_NODE_HTTP in the v4 World docs (#4050) [world-vercel] Honor WORKFLOW_NODE_HTTP on the queue transport (#4044) feat(streams): add WebSocket capability gate (#3764) fix(world-local): retry JSON reads on Windows (#4051) [core] Add the wake-loop scenario to the event log race repro (#4017) [ci] Cap concurrent Vercel E2E action repo-wide (10 by default) (#4039) Add `Run#getWritable()` for appending to another run's stream (#3972) feat(streams): add WebSocket v1 client protocol contract (#3763) [swc-playground] Update to Next.js v16.3.4 (#4018) [core] Add a retention option to start() (#3787) fix(swc-plugin): register class expressions via an IIFE instead of by name (#3971) [docs] Fix prose typos across v4/v5 docs and the SWC plugin README (#3948) Validate pending changesets in CI so a bad one fails the PR, not the Release job (#3964) Version Packages (beta) (#3919) Classify Workflow stream failures (#3850) Drop the ignored @workflow/world-sim package from the hook_conflict delta changeset (#3963) Add attribute inspection to the CLI (#3950) [core] Settle a hook's awaiter in-process instead of re-invoking, on creation and on conflict (#3938) Use the storage APIs for run detail views (#3944) ...
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
WORKFLOW_NODE_HTTPentry todocs/content/worlds/v4/vercel.mdx, and a pointer to it fromdocs/content/worlds/v4/local.mdx.Why
The flag ships in
@workflow/world-vercel@4.7.0(2026-08-19) and is documented only in the v5 docs (docs/content/docs/v5/configuration/runtime-tuning.mdxandworlds/v5/local.mdx). A 4.x user has no way to find it short of reading package source, and the v4 Vercel World page opens with "requires no configuration when deployed to Vercel".That is not hypothetical. It is how the flag was actually found in the field, partway through a nine-day outage on a Pro project whose cause the flag addresses: a Next 16 Turbopack build in which the bundled HTTP client library was unusable, so workflows hung before journaling their first step. Same failure class as #3373.
Where it went
v4 has no consolidated environment-variable page (v5's
configuration/runtime-tuning.mdxhas no v4 counterpart), so the World pages are the only sensible home. The Vercel page carries the full entry and the Local page gets a short entry plus a link, mirroring how v5 splits the same content.The entry covers:
dispatcherpassed tocreateVercelWorld()still wins.Notes
Changeset is empty: docs only, no published package changed. Internal links use the unprefixed
/worlds/vercelform the surrounding v4 pages already use.Docs Preview
/v4/worlds/vercel#workflow_node_http/v4/worlds/local#workflow_node_http🤖 Generated with Claude Code