mia303

This commit performs a **documentation update** for the **Queues** feature, specifically concerning **HTTP pull consumers**. It **removes the outdated Wrangler configuration file method** for enabling HTTP pull from `src/content/docs/queues/configuration/pull-consumers.mdx` and adds a crucial note about its deprecation. This **maintenance** work ensures users are guided to current best practices and prevents reliance on deprecated configuration methods, improving the accuracy and relevance of the **developer documentation**. Minor formatting adjustments are also included to enhance readability.

add-node-types (#29379)

This commit performs a **documentation maintenance** task by **updating the title** of a specific changelog entry. The affected file, `src/content/changelog/workflows/2026-03-06-step-context-available.mdx`, now more accurately reflects that **workflow steps expose retry attempt numbers via step context**. This **title correction** improves the clarity and precision of the **workflow changelog**, making it easier for users to understand new features related to **workflow execution context**.

This commit performs a **documentation update** by correcting the publication date for the `step-context-available` feature within the **workflows changelog**. Specifically, it modifies the entry in `src/content/changelog/workflows/2026-03-06-step-context-available.mdx`, changing the date from '2026-03-03' to '2026-03-06'. This is a minor **maintenance fix** to ensure the accuracy of the historical record presented to users, with no impact on product functionality or behavior.

This commit **documents a new capability** within **Cloudflare Workflows**, specifically the **availability of step context**. It introduces a new changelog entry in `src/content/changelog/workflows/2026-03-06-step-context-available.mdx` to inform users about this enhancement. This **documentation update** ensures that developers leveraging Workflows are aware of the ability to access step-specific data, enabling more sophisticated and state-aware workflow designs. The change primarily affects the **Workflows documentation** and provides crucial information for users building advanced workflows.

This commit re-applies a previously reverted change, effectively increasing the **step limits for Workflows** to 25,000. As part of this **maintenance** effort, the relevant **documentation** in `workers-api.mdx` and `limits.mdx` is updated to reflect this new limit. A **changelog entry** `2026-03-03-step-limits-to-25k.mdx` is also included to record this significant update. This ensures that the intended workflow capabilities are correctly enabled and communicated to users.

This commit **re-applies a previous change** to **increase the maximum number of steps allowed in workflows to 25,000**. This **restores a critical operational limit update** within the **Workflows subsystem**, enabling users to define and execute more complex automation sequences. The work involves **re-introducing a feature enhancement** and **updating related documentation** in `workers-api.mdx` and `limits.mdx` to reflect the new threshold. Additionally, a changelog entry (`2026-03-03-step-limits-to-25k.mdx`) is included to formally record this significant change, providing clearer guidance for developers and users.

This commit **reinstates** a previously reverted change, effectively **increasing the step limits for Workflows** to 25,000. This **maintenance** action ensures that the **Workflows** feature can handle more complex operations by raising its operational ceiling. It also includes crucial **documentation updates** across `workers-api.mdx`, `limits.mdx`, and a dedicated changelog entry (`2026-03-03-step-limits-to-25k.mdx`), ensuring users are aware of the updated capabilities and system constraints. The change directly impacts the scalability of **Workflows** and the accuracy of user-facing **API documentation**.

This commit **reinstates** the increase of **Workflow step limits** to 25,000, effectively reverting a previous revert that had temporarily rolled back this change. It primarily involves **documentation updates** across the `changelog` (`2026-03-03-step-limits-to-25k.mdx`), the `API reference` for `run-workflows.mdx`, and the dedicated `limits.mdx` section for **Workflows**. This **feature reinstatement** allows users to execute significantly more complex automation by raising the maximum number of steps. The updated documentation ensures that developers and users are aware of the new, higher threshold and includes guidance on how to request further increases for advanced use cases, impacting all users of the **Workflows** feature.

This commit **reverts** a previous documentation update, restoring the specified maximum step limit for **Workflows**. It specifically changes the **documentation** in `src/content/docs/agents/api-reference/run-workflows.mdx` and `src/content/docs/workflows/reference/limits.mdx` to reflect a maximum workflow steps limit of **1,024**, down from the previously documented 25,000. This **maintenance** action also removes the section on increasing step limits, ensuring the documentation accurately reflects the current system constraints for workflow execution. The change clarifies the operational limits for users interacting with the **Workflows** feature.

This commit **updates documentation** across the platform to reflect an **increased step limit for Workflows**. Specifically, the maximum number of steps a workflow can execute has been raised to **25,000**, significantly expanding the complexity and scale of operations possible within the **Workflows** subsystem. The changes include a new changelog entry announcing this enhancement, an update to the `run-workflows` API reference documentation, and an adjustment to the general Workflow limits reference, which now also details how to increase these limits. This **documentation update** ensures users and developers are fully informed about the enhanced capabilities and configuration options for their workflows.

This commit provides a **documentation update** across the **Queues documentation** to reflect an increased maximum message delay period. It updates the stated maximum value for message delays from 12 hours to **24 hours** in sections covering batching and retries, queue configuration (`--delivery-delay-secs`), and JavaScript APIs (`delaySeconds`). This **documentation update** ensures users are aware of the expanded capability to configure messages with a significantly longer delay before delivery. The change impacts users configuring queue behavior and sending delayed messages via the API, allowing for more flexible scheduling.

This commit introduces **new documentation** for **Cloudflare Queues**, specifically detailing its **error codes**. It adds a comprehensive page, `error-codes.mdx`, which explains how errors are returned and provides a reference table for various error types, including recommended actions. This **documentation update** significantly improves the developer experience for users integrating with **Cloudflare Queues** by offering clear guidance on error handling. Additionally, it includes a minor **organizational change** to the sidebar order for `wrangler-commands.mdx` within the Queues documentation.

This commit provides **small fixes and updates to the workflow documentation**, specifically addressing content within `trigger-workflows.mdx` which guides users on how to initiate workflows. It also includes an update to `settings.json`, likely related to the documentation's configuration or examples. This **maintenance** work improves the accuracy and clarity of the **workflow subsystem's documentation**, making it easier for users to understand and utilize workflow triggering mechanisms.

This commit performs a **documentation update** to the **Queues limits page** (`src/content/docs/queues/platform/limits.mdx`). It **removes a misleading "Workers Paid" heading** and an orphaned footnote, as the presented limits apply to both Free and Paid plans, with the caution admonition already clarifying distinctions. Additionally, this **maintenance** task clarifies details around message retention and CPU time limits, and removes an outdated API rate limit entry. The changes improve the accuracy and clarity of **Queues service limits** for users, ensuring a better understanding of platform capabilities.

This commit provides a **maintenance fix** by **correcting the date** within the **Changelog** entry for the **Queues free plan**. It specifically updates the date in `src/content/changelog/queues/2026-02-04-queues-free-plan.mdx` to reflect the accurate announcement timeline. This ensures that users referencing the **public changelog** will see the correct publication date for this significant plan update, improving the overall accuracy of release documentation for the **Queues** service.

This commit **updates documentation** across the **Queues** product to reflect the upcoming introduction of a free tier. It modifies several `.mdx` files, including `index.mdx`, `limits.mdx`, `enable-queues.mdx`, and `queues_pricing.mdx`, to clarify pricing, availability, and specific limits for the new **Workers Free plan**. The changes ensure that introductory text, message retention details, enablement descriptions, and the main pricing table accurately represent the free tier's specifics. This **documentation update** provides users with precise information regarding Queues access and costs, particularly for the new free offering.

This commit **adds a new changelog entry** to announce a significant update for **Cloudflare Queues**. Specifically, it documents the **availability of Cloudflare Queues on the Workers Free plan**, making this powerful messaging service accessible to a broader user base. This **documentation update** ensures users are informed about the expanded capabilities of the free tier, impacting the **Cloudflare Workers ecosystem** by enabling more robust application architectures without additional cost. The entry is located at `src/content/changelog/queues/2026-02-04-queues-free-plan.mdx`.

This commit **adds a new changelog entry** for the **Workflows visualizer** feature, introducing a new documentation file at `src/content/changelog/workflows/2026-02-03-workflows-visualizer.mdx`. This **documentation update** details the capabilities and availability of the visualizer, informing users about this new functionality. The change ensures that the project's public changelog accurately reflects the latest enhancements to the **workflows system**.

This commit **updates documentation** by correcting outdated information within the `src/content/docs/workflows/get-started/durable-agents.mdx` guide. It specifically fixes the **template name and repository link** for the durable AI agent example, ensuring users can accurately find and utilize the referenced resources. This **maintenance** task improves the reliability and user experience of the **workflows documentation** by preventing broken links and incorrect references.