Uh oh!
There was an error while loading. Please reload this page.
[docs] Document WORKFLOW_SEQUENTIAL_REPLAYS on the v4 Vercel World page - #2875
Closed
VaguelySerious wants to merge 1 commit into
Closed
[docs] Document WORKFLOW_SEQUENTIAL_REPLAYS on the v4 Vercel World page#2875VaguelySerious wants to merge 1 commit into
VaguelySerious wants to merge 1 commit into
Conversation
The flag ships on the 4.x stable line (#2193), but the docs site deploys from main — without this page the variable is undiscoverable. Covers the build+runtime requirement, the 2x per-delivery billing under maxConcurrency, topic-cardinality/latency costs, and the SDK-only serialization boundary. WORKFLOW_INLINE_OWNERSHIP and WORKFLOW_INLINE_OWNERSHIP_LEASE_SECONDS are already documented on the v5 Runtime Tuning page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
🦋 Changeset detectedLatest commit: 5e82629 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 |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
WORKFLOW_SEQUENTIAL_REPLAYSships on the 4.x stable line ([world-vercel] [builders] Add WORKFLOW_SEQUENTIAL_REPLAYS option to limit flow route concurrency to one #2193), but the docs site deploys frommain— without this page the variable is undiscoverable on the live docs.maxConcurrency(Vercel Queues pricing), topic-cardinality and queueing-latency costs, and the SDK-only serialization boundary.WORKFLOW_INLINE_OWNERSHIPandWORKFLOW_INLINE_OWNERSHIP_LEASE_SECONDSwere checked as part of the same audit and are already documented on the v5 Runtime Tuning configuration page;WORKFLOW_PRECONDITION_GUARDis documented in Add stateUpdatedAt precondition guard to event creation #2266 alongside its implementation.Docs-only; empty changeset included.
Docs Preview
WORKFLOW_SEQUENTIAL_REPLAYS(Preview is behind deployment protection — requires Vercel team access.)
🤖 Generated with Claude Code