[Workflows] Renaming the folder to Platform, adding subrequest limit

public/__redirects

@@ -1921,6 +1921,11 @@
 # workflows
 /workflows/reference/storage-options/ /workers/platform/storage-options/ 301
 /workflows/tutorials/ /workflows/examples 301
+/workflows/reference/changelog/ /workflows/platform/changelog/ 301
+/workflows/reference/glossary/ /workflows/platform/glossary/ 301
+/workflows/reference/limits/ /workflows/platform/limits/ 301
+/workflows/reference/pricing/ /workflows/platform/pricing/ 301
+/workflows/reference/wrangler-commands/ /workflows/platform/wrangler-commands/ 301
 
 # workers KV
 /kv/platform/environments/ /kv/reference/environments/ 301

src/content/changelog/workflows/2025-02-25-workflows-concurrency-increased.mdx

@@ -9,4 +9,4 @@ import { Render, PackageManagers, TypeScriptExample } from "~/components";
 
 [Workflows](/workflows/) now supports up to 4,500 concurrent (running) instances, up from the previous limit of 100. This limit will continue to increase during the Workflows open beta. This increase applies to all users on the Workers Paid plan, and takes effect immediately.
 
-Review the Workflows [limits documentation](/workflows/reference/limits) and/or dive into the [get started guide](/workflows/get-started/guide/) to start building on Workflows.
+Review the Workflows [limits documentation](/workflows/platform/limits) and/or dive into the [get started guide](/workflows/get-started/guide/) to start building on Workflows.

src/content/docs/workflows/build/workers-api.mdx

@@ -103,7 +103,7 @@ Objects that include `Function` or `Symbol` types, and objects with circular ref
 
 `step.sleep` and `step.sleepUntil` methods do not count towards the maximum Workflow steps limit.
 
-More information about the limits imposed on Workflow can be found in the [Workflows limits documentation](/workflows/reference/limits/).
+More information about the limits imposed on Workflow can be found in the [Workflows limits documentation](/workflows/platform/limits/).
 
 :::
 
@@ -224,7 +224,7 @@ Ensure you have a compatibility date `2024-10-22` or later installed when bindin
 
 The `Workflow` type provides methods that allow you to create, inspect the status, and manage running Workflow instances from within a Worker script.
 It is part of the generated types produced by [`wrangler types`](/workers/wrangler/commands/#types).
- 
+
 ```ts title="./worker-configuration.d.ts"
 interface Env {
   // The 'MY_WORKFLOW' variable should match the "binding" value set in the Wrangler config file
@@ -298,7 +298,7 @@ export default {
 
 Create (trigger) a batch of new instance of the given Workflow, up to 100 instances at a time.
 
-This is useful when you are scheduling multiple instances at once. A call to `createBatch` is treated the same as a call to `create` (for a single instance) and allows you to work within the [instance creation limit](/workflows/reference/limits/).
+This is useful when you are scheduling multiple instances at once. A call to `createBatch` is treated the same as a call to `create` (for a single instance) and allows you to work within the [instance creation limit](/workflows/platform/limits/).
 
 * <code>createBatch(batch: WorkflowInstanceCreateOptions[]): Promise&lt;WorkflowInstance[]&gt;</code>
 

src/content/docs/workflows/get-started/cli-quick-start.mdx

@@ -17,7 +17,7 @@ You can build Workflows to post-process file uploads to [R2 object storage](/r2/
 
 :::caution
 
-This guide is for users who are already familiar with Cloudflare Workers the [durable execution](/workflows/reference/glossary/) programming model it enables.
+This guide is for users who are already familiar with Cloudflare Workers the [durable execution](/workflows/platform/glossary/) programming model it enables.
 
 If you are new to either, we recommend the [introduction to Workflows](/workflows/get-started/guide/) guide, which walks you through how a Workflow is defined, how to persist state, and how to deploy and run your first Workflow.
 

src/content/docs/workflows/index.mdx

@@ -70,11 +70,11 @@ Deploy dynamic front-end applications in record time.
 
 <CardGrid>
 
-<LinkTitleCard title="Pricing" href="/workflows/reference/pricing/" icon="seti:shell">
+<LinkTitleCard title="Pricing" href="/workflows/platform/pricing/" icon="seti:shell">
 Learn more about how Workflows is priced.
 </LinkTitleCard>
 
-<LinkTitleCard title="Limits" href="/workflows/reference/limits/" icon="document">
+<LinkTitleCard title="Limits" href="/workflows/platform/limits/" icon="document">
 Learn more about Workflow limits, and how to work within them.
 </LinkTitleCard>
 

src/content/docs/workflows/observability/metrics-analytics.mdx

@@ -42,7 +42,7 @@ The possible values for `eventType` are documented below:
 
 #### Workflows-level status labels
 
-- `WORKFLOW_QUEUED` - the Workflow is queued, but not currently running. This can happen when you are at the [concurrency limit](/workflows/reference/limits/) and new instances are waiting for currently running instances to complete.
+- `WORKFLOW_QUEUED` - the Workflow is queued, but not currently running. This can happen when you are at the [concurrency limit](/workflows/platform/limits/) and new instances are waiting for currently running instances to complete.
 - `WORKFLOW_START` - the Workflow has started and is running.
 - `WORKFLOW_SUCCESS` - the Workflow finished without errors.
 - `WORKFLOW_FAILURE` - the Workflow failed due to errors (exhausting retries, errors thrown, etc).

src/content/docs/workflows/reference/limits.mdx → src/content/docs/workflows/platform/limits.mdx

@@ -29,10 +29,11 @@ Many limits are inherited from those applied to Workers scripts and as documente
 | Maximum number of [queued instances](/workflows/observability/metrics-analytics/#event-types) | 10,000 | 100,000 |
 | Retention limit for completed Workflow state | 3 days | 30 days [^2] |
 | Maximum length of a Workflow ID [^4]         | 64 characters | 64 characters |
+| Maximum number of subrequests per Workflow instance | 50/request | 1000/request |
 
 [^2]: Workflow state and logs will be retained for 3 days on the Workers Free plan and for 7 days on the Workers Paid plan.
 
-[^3]: A Workflow instance can run forever, as long as each step does not take more than the CPU time limit and the maximum number of steps per Workflow is not reached. 
+[^3]: A Workflow instance can run forever, as long as each step does not take more than the CPU time limit and the maximum number of steps per Workflow is not reached.
 
 [^4]: Match pattern: _```^[a-zA-Z0-9_][a-zA-Z0-9-_]*$```_
 

src/content/docs/workflows/reference/pricing.mdx → src/content/docs/workflows/platform/pricing.mdx

@@ -47,7 +47,7 @@ Storage billing for Workflows will go live on September 15th, 2025.
 Storage is billed using gigabyte-month (GB-month) as the billing metric, identical to [Durable Objects SQL storage](/durable-objects/platform/pricing/#sqlite-storage-backend). A GB-month is calculated by averaging the peak storage per day over a billing period (30 days).
 
 * Storage is calculated across all instances, and includes running, errored, sleeping and completed instances.
-* By default, instance state is retained for [3 days on the Free plan](/workflows/reference/limits/) and [7 days on the Paid plan](/workflows/reference/limits/).
+* By default, instance state is retained for [3 days on the Free plan](/workflows/platform/limits/) and [7 days on the Paid plan](/workflows/platform/limits/).
 * When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows.
 * Deleting instances via the [Workers API](/workflows/build/workers-api/), [Wrangler CLI](/workers/wrangler/commands/#workflows), REST API, or dashboard will free up storage. Note that it may take a few minutes for storage limits to update.
 
@@ -75,4 +75,4 @@ Workflows are billed as Workers, and share the same CPU time and request SKUs.
 
 ### Are there any limits to Workflows?
 
-Refer to the published [limits](/workflows/reference/limits/) documentation.
+Refer to the published [limits](/workflows/platform/limits/) documentation.

src/content/glossary/workflows.yaml

@@ -11,7 +11,7 @@ entries:
 
   - term: "step"
     general_definition: |-
-      A step is self-contained, individually retriable component of a Workflow. Steps may emit (optional) state that allows a Workflow to persist and continue from that step, even if a Workflow fails due to a network or infrastructure issue. A Workflow can have one or more steps up to the [step limit](/workflows/reference/limits/).
+      A step is self-contained, individually retriable component of a Workflow. Steps may emit (optional) state that allows a Workflow to persist and continue from that step, even if a Workflow fails due to a network or infrastructure issue. A Workflow can have one or more steps up to the [step limit](/workflows/platform/limits/).
 
   - term: "Event"
     general_definition: |-

src/content/release-notes/workflows.yaml

@@ -1,5 +1,5 @@
 ---
-link: "/workflows/reference/changelog/"
+link: "/workflows/platform/changelog/"
 productName: Workflows
 productLink: "/workflows/"
 productArea: Developer platform