Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@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" + '
feat(core): record replay lineage in run executionContext by mitul-s · Pull Request #2872 · vercel/workflow · GitHub
Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@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('^' + ".*" + ' feat(core): record replay lineage in run executionContext by mitul-s · Pull Request #2872 · vercel/workflow · GitHub
Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@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('^' + ".*" + ' feat(core): record replay lineage in run executionContext by mitul-s · Pull Request #2872 · vercel/workflow · GitHub
Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@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" + ' feat(core): record replay lineage in run executionContext by mitul-s · Pull Request #2872 · vercel/workflow · GitHub
Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@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('^' + ".*" + ' feat(core): record replay lineage in run executionContext by mitul-s · Pull Request #2872 · vercel/workflow · GitHub
Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@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('^' + ".*" + ' feat(core): record replay lineage in run executionContext by mitul-s · Pull Request #2872 · vercel/workflow · GitHub
Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@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); } })(); })(); feat(core): record replay lineage in run executionContext by mitul-s · Pull Request #2872 · vercel/workflow · GitHub
Skip to content

feat(core): record replay lineage in run executionContext - #2872

Merged
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context
Jul 10, 2026
Merged

feat(core): record replay lineage in run executionContext#2872
karthikscale3 merged 7 commits into
mainfrom
c+ms/replay-lineage-execution-context

Conversation

@mitul-s

Copy link
Copy Markdown
Contributor

Summary

Replays currently start a brand-new run with no link back to the run they were replayed from, so tooling can't tell that a run originated as a replay. This adds that link.

  • recreateRunFromExisting now stamps the source run id into the new run's executionContext as replayedFromRunId.
  • start gains an optional replayedFromRunId option (used by recreateRunFromExisting; rarely needed directly) that is merged into the run's executionContext on both the run_created event and the resilient-start queue input.

executionContext is the right home per the repo's own architecture notes ("flexible object that can store arbitrary data without schema changes… flows through all worlds"), and it's already returned on WorkflowRunWithoutData from runs.list, so consumers can read it without resolving full run data.

Motivation

This is the SDK half of a dashboard feature in vercel/front that shows a "Replay of <run id>" indicator next to the workflow name in the all-runs table (mirroring the deployment list's "Redeploy of …"). That PR already reads executionContext.replayedFromRunId; this change is what populates it. Until this lands, the indicator is a no-op because the origin is never recorded.

Changes

  • packages/core/src/runtime/start.ts — add replayedFromRunId? to StartOptionsBase; include it in executionContext when set.
  • packages/core/src/runtime/runs.ts — pass replayedFromRunId: runId from recreateRunFromExisting into start.
  • Tests: start records/omits the key correctly; recreateRunFromExisting forwards the source run id.
  • Changeset (minor, @workflow/core).

Testing

  • pnpm -F @workflow/core vitest run src/runtime/runs.test.ts src/runtime/start.test.ts → 50 passed (incl. 3 new).
  • pnpm -F @workflow/core typecheck → clean.

Notes

  • Observability hydration (hydrateResourceIO) strips executionContext before UI display in this repo's own dashboard; the vercel/front runs list reads world.runs.list directly and is unaffected. If the workflow-repo dashboard should also show this, the value would need to be extracted before stripping (follow-up).

Made with Cursor

recreateRunFromExisting now stamps the source run id into the new run's
executionContext as `replayedFromRunId`, and `start` accepts a matching
option. This lets tooling (e.g. the dashboard runs list) surface a run as
a replay and link back to the run it was replayed from — previously a
replay started a brand-new run with no link to its origin.
Co-authored-by: Cursor <cursoragent@cursor.com>
@mitul-s
mitul-s requested review from a team and ijjk as code ownersJuly 10, 2026 15:13
@vercel

vercelBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@changeset-bot

changeset-botBot commented Jul 10, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 97349f5

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

This PR includes changesets to release 16 packages
NameType
@workflow/coreMinor
@workflow/buildersPatch
@workflow/cliPatch
@workflow/nextPatch
@workflow/nitroPatch
@workflow/vitestPatch
@workflow/web-sharedPatch
@workflow/webPatch
workflowMinor
@workflow/world-testingPatch
@workflow/astroPatch
@workflow/nestPatch
@workflow/nuxtPatch
@workflow/rollupPatch
@workflow/sveltekitPatch
@workflow/vitePatch

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

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

🧪 E2E Test Results

All tests passed

Summary

PassedFailedSkippedTotal
✅ ▲ Vercel Production145302301683
✅ 💻 Local Development161702191836
✅ 📦 Local Production161702191836
✅ 🐘 Local Postgres161702191836
✅ 🪟 Windows15300153
✅ 📋 Other89401771071
Total7351010648415

Details by Category

✅ ▲ Vercel Production
AppPassedFailedSkipped
✅ astro126027
✅ example126027
✅ express126027
✅ fastify126027
✅ hono126027
✅ nextjs-turbopack15003
✅ nextjs-webpack15003
✅ nitro126027
✅ nuxt126027
✅ sveltekit14508
✅ vite126027
✅ 💻 Local Development
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 📦 Local Production
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🐘 Local Postgres
AppPassedFailedSkipped
✅ astro-stable128025
✅ express-stable128025
✅ fastify-stable128025
✅ hono-stable128025
✅ nextjs-turbopack-canary134019
✅ nextjs-turbopack-stable15300
✅ nextjs-webpack-canary134019
✅ nextjs-webpack-stable15300
✅ nitro-stable128025
✅ nuxt-stable128025
✅ sveltekit-stable14706
✅ vite-stable128025
✅ 🪟 Windows
AppPassedFailedSkipped
✅ nextjs-turbopack15300
✅ 📋 Other
AppPassedFailedSkipped
✅ e2e-local-dev-nest-stable128025
✅ e2e-local-dev-tanstack-start-128025
✅ e2e-local-postgres-nest-stable128025
✅ e2e-local-postgres-tanstack-start-128025
✅ e2e-local-prod-nest-stable128025
✅ e2e-local-prod-tanstack-start-128025
✅ e2e-vercel-prod-tanstack-start126027

📋 View full workflow run

@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📊 Workflow Benchmarks

commit 97349f5 · Fri, 10 Jul 2026 20:46:17 GMT · run logs

Backend: vercel · app: nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1203 (+3.5%)1615 🔴1722 🔴2280 🔴30
TTFShook + stream1401 (+11%)1892 🔴1954 🔴1996 🔴30
STSO1020 steps (1-20)305 (+21%)334 🔴351 🔴818 🔴19
STSO1020 steps (101-120)452 (-7.5%)492 🔴654 🔴698 🔴19
STSO1020 steps (1001-1020)854 (-1.1%)886 🔴1015 🔴1044 🔴19
WOstream1203 (+3.5%)16151722228030
WOhook + stream1401 (+11%)18921954199630
SLstream5004 (+1.2%)5631 🔴5819 🔴6829 🔴30
SLhook + stream4669 (-5.1%)5463 🔴5615 🔴6387 🔴30
📜 Previous results (2)

1f516ed

Fri, 10 Jul 2026 18:02:02 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1424 (-1.5%)1779 🔴1828 🔴2055 🔴30
TTFShook + stream1666 (-7.8%)2035 🔴2085 🔴2230 🔴30
STSO1020 steps (1-20)320 (+3.9%)335 🔴358 🔴744 🔴19
STSO1020 steps (101-120)467 (+4.3%)527 🔴588 🔴645 🔴19
STSO1020 steps (1001-1020)889 (±0%)918 🔴1035 🔴1302 🔴19
WOstream1424 (-1.5%)17791828205530
WOhook + stream1666 (-7.8%)20352085223030
SLstream4387 (-11%)4918 🔴5673 🔴6060 🔴30
SLhook + stream4851 (±0%)5445 🔴5642 🔴5887 🔴30

df8ab47

Fri, 10 Jul 2026 15:34:19 GMT · run logs

vercel / nextjs-turbopack

MetricScenarioAvg (ms)P75 (ms)P90 (ms)P99 (ms)Samples
TTFSstream1431 (+22%)1775 🔴1868 🔴2274 🔴30
TTFShook + stream1844 (+34%)2056 🔴2158 🔴2259 🔴30
STSO1020 steps (1-20)301 (+11%)320 🔴454 🔴548 🔴19
STSO1020 steps (101-120)474 (+14%)509 🔴604 🔴918 🔴19
STSO1020 steps (1001-1020)915 (-15%)927 🔴1068 🔴1254 🔴19
WOstream1431 (+22%)17751868227430
WOhook + stream1844 (+34%)20562158225930
SLstream4562 (-7.4%)4850 🔴5765 🔴5899 🔴30
SLhook + stream4678 (-6.9%)4628 🔴5502 🔴5748 🔴30

Avg deltas compare against the most recent benchmark run on main at the time of this run.

Metrics — TTFS: time to first step body execution · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (time outside step bodies, client start → last step body exit) · SL: stream latency (first chunk write → visible to the reader)

Scenarios — stream: one step that streams chunks back to the client; no hooks, so the run stays in turbo mode · hook + stream: registers a hook before the same streaming step, which exits turbo mode · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges

🟢/🔴 mark percentiles within/above target. Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120

TTFS/WO compare client vs deployment clocks and SL compares the step runner’s clock vs the client’s (NTP-synced in CI). WO ends at the last step body exit, the closest observable proxy for the final step-completion request.

Comment threadpackages/core/src/runtime/runs.ts Outdated
Signed-off-by: Mitul Shah <mitulxshah@gmail.com>
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

@mitul-s@VaguelySerious@karthikscale3