Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Use runtime deadline for inline execution limit - #3360

Merged
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration
Aug 5, 2026
Merged

Use runtime deadline for inline execution limit#3360
elliotdauber merged 5 commits into
mainfrom
elliot/max-inline-duration

Conversation

@elliotdauber

@elliotdauberelliotdauber commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Introduces a new getRuntimeDeadline() function to the World interface, and implements it in the Vercel world with getDeadline from @vercel/functions (upgrades @vercel/functions to pick up the latest change)

I went with a tiered inline execution duration based on conversation with the team but I'm open to feedback here. The idea is that with current Vercel limits:

Hobby maxDurations get 2 minutes (same as before)
Pro/ent maxDurations get 5 minutes (raised)
Extended 30 min maxDurations get 10 minutes (raised)

I didn't use the exact times here to calculate the tiers (300 seconds, 800 seconds, 1800 seconds) because by the time we snapshot the current, there will be less than the full maxDuration left.

Has no change to current behavior if the World doesn't implement the new function (max inline execution = 2 minutes)

WORKFLOW_V2_TIMEOUT_MS env var override still takes precendence

This is a rewrite of #2964 which I previously wrote when we were going to use a Vercel-supplied env var for this

@vercel

vercelBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Aug 5, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a4df080

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

This PR includes changesets to release 20 packages
NameType
@workflow/worldPatch
@workflow/world-vercelPatch
@workflow/corePatch
@workflow/cliPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
@workflow/world-localPatch
@workflow/world-postgresPatch
@workflow/world-testingPatch
@workflow/buildersPatch
@workflow/nextPatch
@workflow/nitroPatch
workflowPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch
@workflow/nuxtPatch

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

@socket-security

socket-securityBot commented Aug 5, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

DiffPackageSupply Chain
Security
VulnerabilityQualityMaintenanceLicense
Addednpm/​@​vercel/​functions@​3.8.0991007499100

View full report

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit a4df080 · Wed, 05 Aug 2026 19:11:02 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep1310 (+196%) 🔻1412 🔴 (+25%) 🔻1459 🔴 (±0%)1757 🔴 (+14%)30
TTFSstream1303 (+636%) 🔻1405 🔴 (+33%) 🔻1416 🔴 (+33%) 🔻1456 🔴 (+26%) 🔻30
TTFShook + stream1276 (+2.1%)1690 🔴 (+23%) 🔻1722 🔴 (+21%) 🔻1794 🔴 (+6.7%)30
STSO1020 steps (inline)97 (+14%)146 (+5.0%)167 (+1.8%)345 (+29%) 🔻1019
WO1020 steps162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻162165 (+18%) 🔻1
SLstream latency99 (+18%) 🔻152 🔴 (+35%) 🔻199 🔴 (+42%) 🔻209 🔴 (-42%) 💚30
SOstream overhead (text)127 (+19%) 🔻205 (+26%) 🔻307 (+66%) 🔻921 (+164%) 🔻30
SOstream overhead (structured)141 (+33%) 🔻226 (+49%) 🔻265 (+57%) 🔻899 (+305%) 🔻30
📈 STSO distribution vs main (inline / queue-hop histograms)

1020 steps (inline)

Cumulative STSO time: main 133947ms → this run 160771ms (Δ +26824ms, +20%)

 50-100 ms ┃ main 15 this 1 -14
100-150 ms ██████████████████████┃█ main 827 this 805 -22
150-200 ms ████┃ main 137 this 169 +32
200-250 ms ┃ main 23 this 24 +1
250-300 ms ┃ main 10 this 7 -3
300-350 ms ┃ main 3 this 3 +0
350-400 ms ┃ main 2 this 2 +0
400-450 ms ┃ main 0 this 2 +2
500-550 ms ┃ main 1 this 0 -1
550-600 ms ┃ main 0 this 1 +1
3350-3400 ms ┃ main 0 this 1 +1
3450-3500 ms ┃ main 0 this 1 +1
3500-3550 ms ┃ main 0 this 1 +1
3550-3600 ms ┃ main 0 this 1 +1
4400-4450 ms ┃ main 0 this 1 +1
📜 Previous results (1)

3f4089e

Wed, 05 Aug 2026 18:31:51 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioBest (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstep249 (-44%) 💚1461 🔴 (+29%) 🔻1488 🔴 (+2.3%)1599 🔴 (+3.4%)30
TTFSstream227 (+28%) 🔻1435 🔴 (+35%) 🔻1465 🔴 (+38%) 🔻1643 🔴 (+42%) 🔻30
TTFShook + stream377 (-70%) 💚1592 🔴 (+16%) 🔻1618 🔴 (+13%)1653 🔴 (-1.7%)30
STSO1020 steps (inline)94 (+11%)156 (+12%)177 (+7.9%)337 (+26%) 🔻1019
WO1020 steps152681 (+11%)152681 (+11%)152681 (+11%)152681 (+11%)1
SLstream latency115 (+37%) 🔻164 🔴 (+45%) 🔻177 🔴 (+26%) 🔻224 🔴 (-38%) 💚30
SOstream overhead (text)151 (+41%) 🔻274 🔴 (+68%) 🔻555 🔴 (+200%) 🔻826 (+137%) 🔻30
SOstream overhead (structured)137 (+29%) 🔻389 🔴 (+156%) 🔻639 🔴 (+278%) 🔻810 (+265%) 🔻30
ℹ️ Metric definitions & methodology

The collapsed STSO distribution section above buckets every step gap of the sequential-steps run (not a sampled window), split by whether the step ending the gap ran inline — in the same warm process as the step before it, so the gap is pure framework overhead — or after a queue-hop — the first step of a fresh process, which pays queue dispatch, client reinit and event-log replay. Bars overlay the two runs: is main, marks where this run lands, bridges the gap when this run has more samples in a bucket.

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, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) · SO: stream overhead (end-to-end write+consume time beyond the modelled generation window)

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 · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) · stream overhead (text): writer streams 300 variable-length text token deltas paced at 100/s for 3s (a haiku-size LLM's token throughput) while a parallel reader drains the whole stream; SO is the end-to-end write+consume time beyond the 3s generation window (overhead/backpressure) · stream overhead (structured): same workload as stream overhead (text), but each delta is an AI-SDK-style structured object ({ type: 'text-delta', id, text }) instead of a raw string, so the SO gap vs the text scenario is the added serialization cost

🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · SO 250/500/1000

All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor (clientStart) right before start(), so the CI runner’s request and its path through api.vercel.com sit outside every measured window. TTFS = in-deployment start() → first step body (turbo uses the in-process fast path, non-turbo the dispatch path), and includes the VQS dispatch hop plus any /flow cold start. STSO/WO are measured between step bodies on the deployment. SL is measured inside the workflow (parallel reader/writer steps), so it no longer includes the api.vercel.com read path.

Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the /flow invocation for a large fraction of runs, inflating P75+; the Best column shows the fastest (warm-start) sample for comparison.

@github-actions

github-actionsBot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

E2E Test Summary

Summary
PassedFailedSkippedTotal
✅ ▲ Vercel Production293205003432
✅ 💻 Local Development329004543744
✅ 📦 Local Production329004543744
✅ 🐘 Local Postgres329004543744
✅ 🪟 Windows31200312
✅ 📋 Other206804282496
✅ vercel-multi-region270027
Total152090229017499
Details by Category

✅ ▲ Vercel Production

AppPassedFailedSkipped
✅ astro-node127029
✅ astro-quickjs127029
✅ example-node127029
✅ example-quickjs127029
✅ express-node127029
✅ express-quickjs127029
✅ fastify-node127029
✅ fastify-quickjs127029
✅ hono-node127029
✅ hono-quickjs127029
✅ nextjs-turbopack-node15204
✅ nextjs-turbopack-quickjs15204
✅ nextjs-webpack-node15204
✅ nextjs-webpack-quickjs15204
✅ nitro-node127029
✅ nitro-quickjs127029
✅ nuxt-node127029
✅ nuxt-quickjs127029
✅ sveltekit-node146010
✅ sveltekit-quickjs146010
✅ vite-node127029
✅ vite-quickjs127029

✅ 💻 Local Development

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 📦 Local Production

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🐘 Local Postgres

AppPassedFailedSkipped
✅ astro-stable-node130026
✅ astro-stable-quickjs130026
✅ express-stable-node130026
✅ express-stable-quickjs130026
✅ fastify-stable-node130026
✅ fastify-stable-quickjs130026
✅ hono-stable-node130026
✅ hono-stable-quickjs130026
✅ nextjs-turbopack-canary-node137019
✅ nextjs-turbopack-canary-quickjs137019
✅ nextjs-turbopack-stable-node15600
✅ nextjs-turbopack-stable-quickjs15600
✅ nextjs-webpack-canary-node137019
✅ nextjs-webpack-canary-quickjs137019
✅ nextjs-webpack-stable-node15600
✅ nextjs-webpack-stable-quickjs15600
✅ nitro-stable-node130026
✅ nitro-stable-quickjs130026
✅ nuxt-stable-node130026
✅ nuxt-stable-quickjs130026
✅ sveltekit-stable-node14907
✅ sveltekit-stable-quickjs14907
✅ vite-stable-node130026
✅ vite-stable-quickjs130026

✅ 🪟 Windows

AppPassedFailedSkipped
✅ nextjs-turbopack-node15600
✅ nextjs-turbopack-quickjs15600

✅ 📋 Other

AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable-node130026
✅ e2e-local-dev-nest-stable-quickjs130026
✅ e2e-local-dev-tanstack-start-node130026
✅ e2e-local-dev-tanstack-start-quickjs130026
✅ e2e-local-postgres-nest-stable-node130026
✅ e2e-local-postgres-nest-stable-quickjs130026
✅ e2e-local-postgres-tanstack-start-node130026
✅ e2e-local-postgres-tanstack-start-quickjs130026
✅ e2e-local-prod-nest-stable-node130026
✅ e2e-local-prod-nest-stable-quickjs130026
✅ e2e-local-prod-tanstack-start-node130026
✅ e2e-local-prod-tanstack-start-quickjs130026
✅ e2e-vercel-prod-nest-node127029
✅ e2e-vercel-prod-nest-quickjs127029
✅ e2e-vercel-prod-tanstack-start-node127029
✅ e2e-vercel-prod-tanstack-start-quickjs127029

✅ vercel-multi-region

AppPassedFailedSkipped
✅ nextjs-turbopack2700

📋 View full workflow run

@VaguelySeriousVaguelySerious left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some nits

Optional, and if not already done: we culd modify the docs entry for WORKFLOW_V2_TIMEOUT_MS to mention that we automatically choose this for your platform, but if you already know that you have short/long steps, it might be useful to tune. Also, the page should mention FUNCTION_TIMEOUT error so that AI/SEO finds it when users are seeing these often

Comment threadpackages/world/src/interfaces.ts Outdated

@karthikscale3karthikscale3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Co-authored-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Elliot Dauber <67391073+elliotdauber@users.noreply.github.com>
@elliotdauber
elliotdauber merged commit 72efc90 into mainAug 5, 2026
655 of 677 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

No backport to stable for 72efc90 (AI decision).

This adds a new optional getRuntimeDeadline() method to the World interface, implements it in @workflow/world-vercel, and uses it to raise the inline-execution budget from a flat 2 minutes to a tiered 5/10 minutes — new API surface plus a behavior change to existing defaults, not a defect fix. It also bumps @vercel/functions to ^3.8.0 purely to pick up the new getDeadline capability, which is a routine feature-motivated dependency bump rather than a security or bug fix. Feature work of this kind stays on main.

To override, re-run the Backport to stable workflow manually via workflow_dispatch and paste this commit SHA into the ref input:

72efc90f286956e6cde25b814f9375a8ecbbff36

Sign up for freeto 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.

3 participants

@elliotdauber@VaguelySerious@karthikscale3