Workflows docs updates

public/__redirects

@@ -1966,6 +1966,7 @@
 # Features section
 /workers-ai/markdown-conversion/ /workers-ai/features/markdown-conversion/ 301
 # workflows
+/workflows/get-started/cli-quick-start/ /workflows/get-started/guide/ 301
 /workflows/reference/storage-options/ /workers/platform/storage-options/ 301
 /workflows/tutorials/ /workflows/examples 301
 # workers KV

src/content/docs/workflows/build/rules-of-workflows.mdx

@@ -566,7 +566,7 @@
 	async fetch(req: Request, env: Env): Promise<Response> {
 		let instances = [
 			{ id: "user1", params: { name: "John" } },
 			{ id: "user2", params: { name: "Jane" } },
 			{ id: "user3", params: { name: "Alice" } },
 			{ id: "user4", params: { name: "Bob" } },
 		];
@@ -589,6 +589,10 @@
 
 </TypeScriptExample>
 
+### Limit timeouts to 30 minutes or less
+
+When setting a [WorkflowStep timeout](/workflows/build/workers-api/#workflowstep), ensure that its duration is 30 minutes or less. If your use case requires a timeout greater than 30 minutes, consider using `step.waitForEvent()` instead.
+
 ### Keep step return values under 1 MiB
 
 Each step can persist up to 1 MiB (2^20 bytes) of state. If your step returns data exceeding this limit, the step will fail. This is a common issue when fetching large API responses or processing large files.

src/content/docs/workflows/build/trigger-workflows.mdx

@@ -204,4 +204,4 @@ Refer to the [Workflows REST API documentation](/api/resources/workflows/subreso
 
 ## Command line (CLI)
 
-Refer to the [CLI quick start](/workflows/get-started/cli-quick-start/) to learn more about how to manage and trigger Workflows via the command-line.
+Refer to the [CLI quick start](/workflows/get-started/guide/) to learn more about how to manage and trigger Workflows via the command-line.