limits

Author: elithrar

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

@@ -84,7 +84,7 @@ When returning state from a `step`, ensure that the object you return is _serial
 
 Primitive types like `string`, `number`, and `boolean`, along with composite structures such as `Array` and `Object` (provided they only contain serializable values), can be serialized.
 
-Objects that include `Function` or `Symbol` types, and objects with circular references, cannot be serialized and the Workflow instance will throw an error if objects with those types is returned. 
+Objects that include `Function` or `Symbol` types, and objects with circular references, cannot be serialized and the Workflow instance will throw an error if objects with those types is returned.
 
 :::
 
@@ -133,12 +133,6 @@ Refer to the [documentation on sleeping and retrying](/workflows/build/sleeping-
 
 ## Call Workflows from Workers
 
-:::note[Workflows beta]
-
-Workflows currently requires you to bind to a Workflow via the [Wrangler configuration file](/workers/wrangler/configuration/), and does not yet support bindings via the Workers dashboard.
-
-:::
-
 Workflows exposes an API directly to your Workers scripts via the [bindings](/workers/runtime-apis/bindings/#what-is-a-binding) concept. Bindings allow you to securely call a Workflow without having to manage API keys or clients.
 
 You can bind to a Workflow by defining a `[[workflows]]` binding within your Wrangler configuration.
@@ -286,7 +280,7 @@ This is useful when you are scheduling multiple instances at once. A call to `cr
 
   * `batch` - list of Options to pass when creating an instance, including a user-provided ID and payload parameters.
 
-Each element of the `batch` list is expected to the 
+Each element of the `batch` list is expected to the
 
 ```ts
 // Create a new batch of 3 Workflow instances, each with its own ID and pass params to the Workflow instances

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

@@ -9,14 +9,6 @@ sidebar:
 
 import { Render, PackageManagers, WranglerConfig } from "~/components"
 
-:::note
-
-Workflows is in **public beta**, and any developer with a [free or paid Workers plan](/workers/platform/pricing/#workers) can start using Workflows immediately.
-
-To learn more about Workflows and how it works, read [the beta announcement blog](https://blog.cloudflare.com/building-workflows-durable-execution-on-workers).
-
-:::
-
 Workflows allow you to build durable, multi-step applications using the Workers platform. A Workflow can automatically retry, persist state, run for hours or days, and coordinate between third-party APIs.
 
 You can build Workflows to post-process file uploads to [R2 object storage](/r2/), automate generation of [Workers AI](/workers-ai/) embeddings into a [Vectorize](/vectorize/) vector database, or to trigger user lifecycle emails using your favorite email API.

src/content/docs/workflows/get-started/guide.mdx

@@ -9,14 +9,6 @@ sidebar:
 
 import { Render, PackageManagers, WranglerConfig } from "~/components"
 
-:::note
-
-Workflows is in **public beta**, and any developer with a [free or paid Workers plan](/workers/platform/pricing/#workers) can start using Workflows immediately.
-
-To learn more about Workflows and how it works, read [the beta announcement blog](https://blog.cloudflare.com/building-workflows-durable-execution-on-workers).
-
-:::
-
 Workflows allow you to build durable, multi-step applications using the Workers platform. A Workflow can automatically retry, persist state, run for hours or days, and coordinate between third-party APIs.
 
 You can build Workflows to post-process file uploads to [R2 object storage](/r2/), automate generation of [Workers AI](/workers-ai/) embeddings into a [Vectorize](/vectorize/) vector database, or to trigger user lifecycle emails using your favorite email API.

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

@@ -22,17 +22,15 @@ Many limits are inherited from those applied to Workers scripts and as documente
 | Maximum event [payload size](/workflows/build/events-and-parameters/) | 1MiB (2^20 bytes) | 1MiB (2^20 bytes) |
 | Maximum state that can be persisted per Workflow instance | 100MB | 1GB |
 | Maximum length of a Workflow ID [^4]      | 64 characters | 64 characters |
-| Maximum `step.sleep` duration             | 365 days (1 year) [^1] | 365 days (1 year) [^1] |
-| Maximum steps per Workflow [^5]           | 1024 [^1] | 1024 [^1] |
+| Maximum `step.sleep` duration             | 365 days (1 year) | 365 days (1 year) |
+| Maximum steps per Workflow [^5]           | 1024 | 1024 |
 | Maximum Workflow executions               | 100,000 per day [shared with Workers daily limit](/workers/platform/limits/#worker-limits) | Unlimited |
-| Concurrent Workflow instances (executions) per account   | 25 | 4500 [^1] |
-| Maximum Workflow instance creation rate | 100 per 10 seconds [^1][^6] | 100 per 10 seconds [^1][^6] | 
-| Maximum number of [queued instances](/workflows/observability/metrics-analytics/#event-types) | 10,000 [^1] | 100,000 [^1] |
+| Concurrent Workflow instances (executions) per account   | 25 | 4500 |
+| Maximum Workflow instance creation rate | 100 per 10 seconds [^6] | 100 per 10 seconds [^6] |
+| 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 |
 
-[^1]: This limit will be reviewed and revised during the open beta for Workflows. Follow the [Workflows changelog](/workflows/reference/changelog/) for updates.
-
 [^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.