Skip to content

docs: Add durable streaming migration guide, FAQ, and content enhancements#1323

Open
johnlindquist wants to merge 4 commits intomainfrom
docs/workflow-streaming-content
Open

docs: Add durable streaming migration guide, FAQ, and content enhancements#1323
johnlindquist wants to merge 4 commits intomainfrom
docs/workflow-streaming-content

Conversation

@johnlindquist
Copy link
Copy Markdown
Contributor

Summary

  • New: Migration guide (foundations/migrate-ephemeral-streaming.mdx) — Step-by-step guide for moving from ephemeral streaming to durable streaming with Workflow DevKit. Covers wrapping generation in a workflow step, exposing runId, swapping in WorkflowChatTransport, and common gotchas.
  • New: FAQ section (faq/index.mdx) — 13 questions covering troubleshooting (silent step failures, WorkflowChatTransport body shape), migration (incremental adoption, what you get after migrating), compatibility (local dev, AI SDK, frameworks, DurableAgent), and advanced usage (reconnection flow, user input hooks, redeploy behavior, multiple clients).
  • Enhanced: foundations/streaming.mdx — Added "Why durable streaming" section explaining the durability model vs ephemeral connections, with links to migration guide and resumable streams.
  • Enhanced: ai/resumable-streams.mdx — Added common gotchas callout for WorkflowChatTransport request body customization via prepareSendMessagesRequest, and local debugging tips using the Web UI.
  • Enhanced: deploying/world/local-world.mdx — Added "Why local development matters" section highlighting the step debugger for catching silent failures during development.
  • Enhanced: observability/index.mdx — Added debugging walkthrough for silent step failures using the Web UI, with step-by-step instructions.

Context

Based on real developer feedback from a Workflow migration (async-recipes app). The feedback identified these gaps:

  • No migration path from ephemeral to durable streaming
  • No FAQ or troubleshooting content
  • WorkflowChatTransport gotchas not documented near usage examples
  • "Works locally" story not prominent enough in local dev and observability docs

Test plan

  • Verify new pages render correctly in the docs site (npm run dev)
  • Verify navigation: migration guide appears under Foundations after Streaming
  • Verify navigation: FAQ appears in top-level nav before API Reference
  • Verify all internal links resolve (migration guide, FAQ cross-references)
  • Verify existing pages still render after enhancements (streaming, resumable-streams, local-world, observability)

@johnlindquist johnlindquist requested a review from a team as a code owner March 11, 2026 03:30
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Mar 11, 2026

⚠️ No Changeset found

Latest commit: 05ee680

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Mar 11, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
example-nextjs-workflow-turbopack Ready Ready Preview, Comment Apr 6, 2026 10:13pm
example-nextjs-workflow-webpack Ready Ready Preview, Comment Apr 6, 2026 10:13pm
example-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-astro-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-express-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-fastify-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-hono-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-nitro-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-nuxt-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-sveltekit-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workbench-vite-workflow Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workflow-docs Ready Ready Preview, Comment, Open in v0 Apr 6, 2026 10:13pm
workflow-nest Ready Ready Preview, Comment Apr 6, 2026 10:13pm
workflow-swc-playground Ready Ready Preview, Comment Apr 6, 2026 10:13pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 11, 2026

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.056s (-4.9%) 1.010s (~) 0.954s 10 1.00x
🐘 Postgres Express 0.058s (-4.3%) 1.010s (~) 0.952s 10 1.04x
workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.144s (~) 2.009s (~) 0.865s 10 1.00x
🐘 Postgres Express 1.149s (~) 2.007s (~) 0.859s 10 1.00x
workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 10.879s (~) 11.023s (~) 0.144s 3 1.00x
🐘 Postgres Nitro 10.918s (~) 11.026s (~) 0.109s 3 1.00x
workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 14.578s (~) 15.022s (~) 0.444s 4 1.00x
🐘 Postgres Nitro 14.587s (~) 15.026s (~) 0.439s 4 1.00x
workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 13.993s (-1.4%) 14.447s (-2.9%) 0.455s 7 1.00x
🐘 Postgres Nitro 14.161s (+1.1%) 15.023s (+6.0% 🔺) 0.862s 6 1.01x
Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 1.249s (-2.9%) 2.010s (~) 0.761s 15 1.00x
🐘 Postgres Nitro 1.262s (~) 2.009s (~) 0.747s 15 1.01x
Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 2.309s (-1.1%) 3.009s (~) 0.701s 10 1.00x
🐘 Postgres Express 2.318s (~) 3.008s (~) 0.690s 10 1.00x
Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 3.449s (-1.1%) 4.009s (~) 0.560s 8 1.00x
🐘 Postgres Express 3.482s (~) 4.010s (~) 0.528s 8 1.01x
Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.249s (+0.5%) 2.007s (~) 0.758s 15 1.00x
🐘 Postgres Express 1.276s (+1.5%) 2.008s (~) 0.732s 15 1.02x
Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 2.299s (-1.0%) 3.009s (~) 0.711s 10 1.00x
🐘 Postgres Express 2.325s (-1.3%) 3.009s (~) 0.683s 10 1.01x
Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 3.443s (-0.8%) 4.013s (~) 0.570s 8 1.00x
🐘 Postgres Express 3.472s (-0.7%) 4.012s (~) 0.540s 8 1.01x
workflow with 10 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 0.817s (-5.3% 🟢) 1.006s (-1.8%) 0.189s 60 1.00x
🐘 Postgres Nitro 0.851s (+1.9%) 1.006s (~) 0.155s 60 1.04x
workflow with 25 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 1.979s (-5.6% 🟢) 2.340s (-19.6% 🟢) 0.361s 39 1.00x
🐘 Postgres Nitro 2.048s (+4.1%) 2.535s (+12.3% 🔺) 0.488s 36 1.03x
workflow with 50 sequential data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 3.969s (-0.8%) 4.296s (-0.8%) 0.327s 28 1.00x
🐘 Postgres Express 4.032s (-4.3%) 4.528s (-9.0% 🟢) 0.496s 27 1.02x
workflow with 10 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.275s (-0.9%) 1.007s (~) 0.731s 60 1.00x
🐘 Postgres Express 0.286s (-0.5%) 1.007s (~) 0.721s 60 1.04x
workflow with 25 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.474s (-3.6%) 1.006s (~) 0.532s 90 1.00x
🐘 Postgres Express 0.488s (-0.7%) 1.007s (~) 0.518s 90 1.03x
workflow with 50 concurrent data payload steps (10KB)

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.780s (~) 1.007s (~) 0.227s 120 1.00x
🐘 Postgres Express 0.785s (-2.7%) 1.016s (+0.6%) 0.230s 119 1.01x
Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Express 0.199s (-8.6% 🟢) 0.996s (~) 0.001s (+7.7% 🔺) 1.009s (~) 0.810s 10 1.00x
🐘 Postgres Nitro 0.207s (+1.8%) 0.995s (~) 0.001s (-23.1% 🟢) 1.009s (~) 0.803s 10 1.04x
stream pipeline with 5 transform steps (1MB)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.607s (-2.1%) 1.002s (~) 0.004s (+32.7% 🔺) 1.020s (~) 0.414s 59 1.00x
🐘 Postgres Express 0.610s (+0.6%) 1.004s (~) 0.004s (+5.5% 🔺) 1.021s (~) 0.412s 59 1.01x
10 parallel streams (1MB each)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 0.935s (-1.6%) 1.149s (-3.9%) 0.000s (+284.6% 🔺) 1.161s (-3.9%) 0.227s 52 1.00x
🐘 Postgres Express 0.942s (-1.1%) 1.214s (+3.8%) 0.000s (+2.0%) 1.230s (+3.8%) 0.288s 50 1.01x
fan-out fan-in 10 streams (1MB each)

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
🐘 Postgres 🥇 Nitro 1.687s (-4.8%) 2.101s (~) 0.000s (+Infinity% 🔺) 2.113s (-1.4%) 0.426s 29 1.00x
🐘 Postgres Express 1.723s (-2.5%) 2.139s (+3.1%) 0.000s (-48.2% 🟢) 2.152s (+2.1%) 0.429s 28 1.02x

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
🐘 Postgres Nitro 14/21
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 🐘 Postgres 21/21
Nitro 🐘 Postgres 21/21
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run


Some benchmark jobs failed:

  • Local: failure
  • Postgres: success
  • Vercel: cancelled

Check the workflow run for details.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 11, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
✅ ▲ Vercel Production 846 0 67 913
✅ 💻 Local Development 818 0 178 996
✅ 📦 Local Production 818 0 178 996
✅ 🐘 Local Postgres 818 0 178 996
✅ 🪟 Windows 75 0 8 83
❌ 🌍 Community Worlds 135 63 24 222
✅ 📋 Other 207 0 42 249
Total 3717 63 675 4455

❌ Failed Tests

🌍 Community Worlds (63 failed)

mongodb (3 failed):

  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNJDQQPC32NWAJVWBHT819M0
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNJE06AVFQTD5GD124XYVZEF
  • resilient start: addTenWorkflow completes when run_created returns 500

redis (3 failed):

  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNJDQQPC32NWAJVWBHT819M0
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNJE06AVFQTD5GD124XYVZEF
  • resilient start: addTenWorkflow completes when run_created returns 500

turso (57 failed):

  • addTenWorkflow | wrun_01KNJDPDEE2MQT17JYNQY6SE1K
  • addTenWorkflow | wrun_01KNJDPDEE2MQT17JYNQY6SE1K
  • wellKnownAgentWorkflow (.well-known/agent) | wrun_01KNJDQS1CS34CSM1GKT9F4KV9
  • should work with react rendering in step
  • promiseAllWorkflow | wrun_01KNJDPMNZ8ARCT6G23B4SVX24
  • promiseRaceWorkflow | wrun_01KNJDPT8ASK5YRHS9J2F5G8G2
  • promiseAnyWorkflow | wrun_01KNJDPWHXP4SV2F0D07VY8JV5
  • importedStepOnlyWorkflow | wrun_01KNJDR6GFSN08294X6HTY8KDN
  • hookWorkflow | wrun_01KNJDQB5V06RAPABSASPD8HPV
  • hookWorkflow is not resumable via public webhook endpoint | wrun_01KNJDQQPC32NWAJVWBHT819M0
  • webhookWorkflow | wrun_01KNJDR0QYH76G111HAA7FY9N1
  • sleepingWorkflow | wrun_01KNJDR74NGBM7XG38ZYYEPVHN
  • parallelSleepWorkflow | wrun_01KNJDRM3174KGYXA8GM9GM2A6
  • nullByteWorkflow | wrun_01KNJDRRQN25DEMQZSPP747FKJ
  • workflowAndStepMetadataWorkflow | wrun_01KNJDRWAMWZFF3K4CP63V67NT
  • fetchWorkflow | wrun_01KNJDVJ8QR2PFEAW33PY0Q2W6
  • promiseRaceStressTestWorkflow | wrun_01KNJDVQ6NJZ5EYEDMJ8H2KE1Z
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • error handling not registered WorkflowNotRegisteredError fails the run when workflow does not exist
  • error handling not registered StepNotRegisteredError fails the step but workflow can catch it
  • error handling not registered StepNotRegisteredError fails the run when not caught in workflow
  • hookCleanupTestWorkflow - hook token reuse after workflow completion | wrun_01KNJDZH319DSZ5R7805WKHQWM
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously | wrun_01KNJE06AVFQTD5GD124XYVZEF
  • hookDisposeTestWorkflow - hook token reuse after explicit disposal while workflow still running | wrun_01KNJE0VBZPG1J4WF7HCBJKSS1
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars) | wrun_01KNJE1FHF2ZEX6Q776201392M
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument | wrun_01KNJE1RVWMG29CJ3PXCWMGNXX
  • closureVariableWorkflow - nested step functions with closure variables | wrun_01KNJE1YHD419N632ZXM6DYQD5
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step | wrun_01KNJE20XG97DHSZTDQCM2S950
  • health check (queue-based) - workflow and step endpoints respond to health check messages
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly | wrun_01KNJE2H8YAMP7X5D1FGPQB54E
  • Calculator.calculate - static workflow method using static step methods from another class | wrun_01KNJE2Q90FBR3WBWR0A1QYXGB
  • AllInOneService.processNumber - static workflow method using sibling static step methods | wrun_01KNJE2Y45RVXBN31Q0RQTMGZ4
  • ChainableService.processWithThis - static step methods using this to reference the class | wrun_01KNJE33QKBXEAW0J7QT31WT2H
  • thisSerializationWorkflow - step function invoked with .call() and .apply() | wrun_01KNJE39HSJT9NRNPKXG3HKZ3W
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE | wrun_01KNJE3HX4KSCRT8CQBWCJFQAP
  • instanceMethodStepWorkflow - instance methods with "use step" directive | wrun_01KNJE3RWAT30CYWNREJP6V9KN
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context | wrun_01KNJE44MQR1H623ZSG73NC5Q9
  • stepFunctionAsStartArgWorkflow - step function reference passed as start() argument | wrun_01KNJE4DV2KJK8W5BF60ZKBD5J
  • cancelRun - cancelling a running workflow | wrun_01KNJE4MXT0GS9ZRDXCTM4D5P8
  • cancelRun via CLI - cancelling a running workflow | wrun_01KNJE4YEA42WM6F0P1D2XQBZF
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router
  • hookWithSleepWorkflow - hook payloads delivered correctly with concurrent sleep | wrun_01KNJE5APBAK78KS7JXDYWHW8J
  • sleepInLoopWorkflow - sleep inside loop with steps actually delays each iteration | wrun_01KNJE60KCWVWT239G3AZYQXSD
  • sleepWithSequentialStepsWorkflow - sequential steps work with concurrent sleep (control) | wrun_01KNJE6B11QEDRAQZMHTQ4DQ6M
  • importMetaUrlWorkflow - import.meta.url is available in step bundles
  • metadataFromHelperWorkflow - getWorkflowMetadata/getStepMetadata work from module-level helper (#1577)
  • resilient start: addTenWorkflow completes when run_created returns 500

Details by Category

✅ ▲ Vercel Production
App Passed Failed Skipped
✅ astro 76 0 7
✅ example 76 0 7
✅ express 76 0 7
✅ fastify 76 0 7
✅ hono 76 0 7
✅ nextjs-turbopack 81 0 2
✅ nextjs-webpack 81 0 2
✅ nitro 76 0 7
✅ nuxt 76 0 7
✅ sveltekit 76 0 7
✅ vite 76 0 7
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 69 0 14
✅ express-stable 69 0 14
✅ fastify-stable 69 0 14
✅ hono-stable 69 0 14
✅ nextjs-turbopack-canary 58 0 25
✅ nextjs-turbopack-stable 75 0 8
✅ nextjs-webpack-canary 58 0 25
✅ nextjs-webpack-stable 75 0 8
✅ nitro-stable 69 0 14
✅ nuxt-stable 69 0 14
✅ sveltekit-stable 69 0 14
✅ vite-stable 69 0 14
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 69 0 14
✅ express-stable 69 0 14
✅ fastify-stable 69 0 14
✅ hono-stable 69 0 14
✅ nextjs-turbopack-canary 58 0 25
✅ nextjs-turbopack-stable 75 0 8
✅ nextjs-webpack-canary 58 0 25
✅ nextjs-webpack-stable 75 0 8
✅ nitro-stable 69 0 14
✅ nuxt-stable 69 0 14
✅ sveltekit-stable 69 0 14
✅ vite-stable 69 0 14
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 69 0 14
✅ express-stable 69 0 14
✅ fastify-stable 69 0 14
✅ hono-stable 69 0 14
✅ nextjs-turbopack-canary 58 0 25
✅ nextjs-turbopack-stable 75 0 8
✅ nextjs-webpack-canary 58 0 25
✅ nextjs-webpack-stable 75 0 8
✅ nitro-stable 69 0 14
✅ nuxt-stable 69 0 14
✅ sveltekit-stable 69 0 14
✅ vite-stable 69 0 14
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 75 0 8
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 5 0 0
❌ mongodb 58 3 8
✅ redis-dev 5 0 0
❌ redis 58 3 8
✅ turso-dev 5 0 0
❌ turso 4 57 8
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 69 0 14
✅ e2e-local-postgres-nest-stable 69 0 14
✅ e2e-local-prod-nest-stable 69 0 14

📋 View full workflow run

Use DurableAgent string model IDs ("anthropic/claude-haiku-4.5") instead
of AI SDK provider functions (openai("gpt-4o")) in new docs content.
- Use workflow-level getWritable() instead of wrapping in a step
- DurableAgent internally creates steps, no manual "use step" needed
- Use ModelMessage type with convertToModelMessages
- Split workflow definition and route handler into separate files
  matching the pattern in ai/index.mdx
- resumable-streams.mdx: clarify run does not need to be active to
  connect to a stream (per VaguelySerious)
- faq/index.mdx: same correction for reconnection troubleshooting
- faq/index.mdx: update deployment FAQ answer — Vercel World runs
  continue on their original deployment, not just "survive"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants