docs: improve troubleshooting pages (#1540)

Author: lgrammel

content/docs/08-troubleshooting/01-common-issues/04-strange-stream-output.mdx

@@ -1,9 +1,9 @@
 ---
-title: Strange Stream Output
+title: useChat/useCompletion stream output contains 0:... instead of text
 description: How to fix strange stream output in the UI
 ---
 
-# Strange Stream Outputs
+# useChat/useCompletion stream output contains 0:... instead of text
 
 ## Issue
 

content/docs/08-troubleshooting/01-common-issues/06-streaming-not-working-in-production.mdx

@@ -0,0 +1,21 @@
+---
+title: Streaming Not Working When Deploying on Vercel
+description: Troubleshooting errors related to streaming not working when deploying on Vercel.
+---
+
+# Streaming Not Working When Deploying on Vercel
+
+## Issue
+
+Streaming with the AI SDK works in my local dev environment. I'm using the app router and I'm deploying to Vercel.
+However, streaming does not work in the deployed app. Instead of streaming, only the full response is returned after a while.
+
+## Solution
+
+Add the following to your route file:
+
+```tsx
+export const dynamic = 'force-dynamic';
+```
+
+This will enforce dynamic behavior, which is required for streaming.

content/docs/08-troubleshooting/01-common-issues/06-streaming-not-working-on-vercel.mdx

@@ -0,0 +1,27 @@
+---
+title: Getting Timeouts When Deploying on Vercel
+description: Troubleshooting errors related to streaming not working when deploying on Vercel.
+---
+
+# Getting Timeouts When Deploying on Vercel
+
+## Issue
+
+Streaming with the AI SDK works in my local dev environment.
+I'm using the app router and I'm deploying to Vercel.
+However, I'm getting timeouts.
+
+## Solution
+
+Add the following to your route file:
+
+```tsx
+export const maxDuration = 60;
+export const dynamic = 'force-dynamic';
+```
+
+This will enforce dynamic behavior, which is required for streaming.
+
+## See also
+
+- [Configuring Maximum Duration for Vercel Functions](https://vercel.com/docs/functions/configuring-functions/duration)

content/docs/08-troubleshooting/01-common-issues/06-timeout-on-vercel.mdx

@@ -13,11 +13,12 @@ Sometimes streams are not closed properly, which can lead to unexpected behavior
 
 ## Solution
 
-This happens when you create a streamable UI using [`createStreamableUI`](/docs/reference/ai-sdk-rsc/create-streamable-ui) and fail to close the stream. In order to fix this, you must ensure you close the stream by calling the [`.done()`](/docs/reference/ai-sdk-rsc/create-streamable-ui#done) method. This will ensure the stream is closed.
+This happens when you create a streamable UI using [`createStreamableUI`](/docs/reference/ai-sdk-rsc/create-streamable-ui) and fail to close the stream.
+In order to fix this, you must ensure you close the stream by calling the [`.done()`](/docs/reference/ai-sdk-rsc/create-streamable-ui#done) method.
+This will ensure the stream is closed.
 
 ```tsx file='app/actions.ts'
 import { createStreamableUI } from 'ai/rsc';
-import { nanoid } from 'nanoid';
 
 const submitMessage = async () => {
   'use server';
@@ -28,9 +29,6 @@ const submitMessage = async () => {
   stream.append('3');
   stream.done('4'); // [!code ++]
 
-  return {
-    id: nanoid(),
-    display: stream.value,
-  };
+  return stream.value,
 };
 ```

content/docs/08-troubleshooting/01-common-issues/07-unclosed-streams.mdx

@@ -7,15 +7,19 @@ description: Troubleshooting errors related to the Use Chat Failed to Parse Stre
 
 ## Issue
 
-I am using `useChat` or `useCompletion` and I’m getting a `"Failed to parse stream string. Invalid code"` error. I am using version `3.0.20` or newer of the AI SDK.
+I am using `useChat` or `useCompletion` and I am getting a `"Failed to parse stream string. Invalid code"` error. I am using version `3.0.20` or newer of the AI SDK.
 
 ## Background
 
-The AI SDK has switched to the stream data protocol in version `3.0.20` . `useChat` and `useCompletion` expect stream parts that support data, tool calls, etc. What you see is a failure to parse the stream. This can be caused by using an older version of the AI SDK in the backend, by providing a text stream using a custom provider, or by using a raw LangChain stream result.
+The AI SDK has switched to the stream data protocol in version `3.0.20`.
+`useChat` and `useCompletion` expect stream parts that support data, tool calls, etc.
+What you see is a failure to parse the stream.
+This can be caused by using an older version of the AI SDK in the backend, by providing a text stream using a custom provider, or by using a raw LangChain stream result.
 
 ## Solution
 
-You can switch `useChat` and `useCompletion` to raw text stream processing with the `streamMode` parameter (introduced in `v3.0.23` of the AI SDK). Just set it to `text` as follows:
+You can switch `useChat` and `useCompletion` to raw text stream processing with the `streamMode` parameter (introduced in `v3.0.23` of the AI SDK).
+Set it to `text` as follows:
 
 ```tsx
 const { messages, append } = useChat({