Setting the file. One moment.
Subchapter 7.59
references/support-topics/workflow-resumable-stream-routes.mdMarkdown1 KBView on GitHub
Stream-shaped routes may be Workflow SDK reconnection endpoints. Long wall-clock duration can be the live client connection.
Look for WorkflowChatTransport, getRun, run.getReadable, startIndex, x-workflow-run-id, x-workflow-stream-tail-index, getWritable, or createUIMessageStreamResponse. Compare CPU, TTFB, wall-clock. Check full replay, missing tail-index, unreleased locks, or unclosed streams.
Do not cache stream endpoints or remove resumability. Do not call high duration a bug when CPU is low, TTFB is healthy, and the route only holds a client connection.
Name whether the route starts or reconnects a run, then cite the exact waste: replay, missing tail-index, lock leak, unclosed stream, high CPU, or avoidable pre-first-byte work.