Olga Silva

This commit introduces **local development capabilities** for **Cloudflare Workflows** within the `wrangler` CLI, allowing developers to test their workflows without deploying them. This **new feature** significantly enhances the developer experience by adding a `--local` option to `wrangler workflows` commands. The change includes comprehensive **documentation updates** across changelogs, command references (`src/content/docs/workers/wrangler/commands/workflows.mdx`), and release notes, alongside a minor `wrangler` dependency version bump. This enables more efficient iteration and debugging of Workflows locally before deployment.

This commit introduces **local development capabilities** for **Cloudflare Workflows** within the **Wrangler CLI**. It implements a new `--local` flag across various `wrangler workflows` commands, including `list`, `describe`, `trigger`, `delete`, and all `instances` subcommands, enabling developers to interact with workflows running in a local development session. This **new feature** significantly enhances the local development experience by allowing direct management and testing of workflows without requiring deployment to a remote environment. New utility functions in `packages/wrangler/src/workflows/local.ts` facilitate this local interaction, supported by comprehensive new test suites.

This commit introduces **comprehensive Workflows support** to the **Local Explorer UI** and its underlying **Miniflare** backend. It adds a new **Workflows section to the sidebar** and dedicated routes within `packages/local-explorer-ui` for displaying workflow lists, individual workflow details, and instance details, complete with new UI components like `WorkflowStatusBadge` and `StepRow`. Concurrently, `packages/miniflare` gains internal methods for workflow instance persistence, extended explorer plugin logic, and new API endpoints in the local explorer worker to manage and expose workflow data. This **new capability** significantly enhances the local development experience by allowing users to **view, manage, and interact with Workflows and their instances directly within the UI**.

This commit provides a **documentation update** for the **Workflows** feature, announcing the availability of **instance methods** for local development environments. It adds new entries to both the changelog (`src/content/changelog/workflows/2026-03-23-local-dev-instance-methods.mdx`) and release notes (`src/content/release-notes/workflows.yaml`), informing users that they can now utilize methods such as `pause`, `resume`, `restart`, and `terminate` when developing Workflows locally. This update enhances the developer experience by clarifying the capabilities of the local Workflow development environment.

This commit delivers a crucial **bug fix** within the **`workflows-shared`** package, addressing an issue where `waitForEvent` could erroneously deliver events to "stale" waiters that had already timed out. The `waitForEvent` implementation in `packages/workflows-shared/src/context.ts` was modified to correctly manage and remove event resolvers, ensuring proper cleanup after a timeout. Concurrently, the `receiveEvent` logic in `packages/workflows-shared/src/engine.ts` was updated to accommodate the new resolver structure, preventing future misdeliveries. A new test case in `packages/workflows-shared/tests/engine.test.ts` validates that events are no longer consumed by timed-out listeners, significantly **improving the reliability and correctness of event handling** within workflows.

This commit **implements core instance lifecycle methods** for the **Workflows subsystem**, enabling programmatic control over running workflow instances. It introduces `pause`, `resume`, `terminate`, and `restart` functionalities, with the core logic integrated into the `packages/workflows-shared` engine and binding. The changes extend to `packages/miniflare` for local development support and update `packages/vitest-pool-workers` to correctly handle new workflow states like 'terminated' and 'paused'. This **new capability** is thoroughly validated with extensive **unit and integration tests** across various fixtures, significantly enhancing the manageability and flexibility of workflows.

This commit introduces **new capabilities** for managing **Workflows instances**, allowing users to **pause, resume, restart, and terminate** running workflows. The core logic for these lifecycle methods is implemented within the `workflows-shared` package, handling state transitions, storage, and error management. These new instance methods are exposed through `WorkflowHandle` and integrated into `Miniflare` via `wrapped-binding.worker.ts` for local development. Extensive integration tests have been added across various fixtures, and the `vitest-pool-workers` now supports waiting for `terminated` and `paused` states, significantly enhancing workflow control and testability.

This commit re-introduces the `WorkflowStepContext` to the `step.do` callback, providing a new capability for developers to access additional contextual data within workflow step implementations. This affects how workflow steps can be designed and implemented.

Adds a new capability to the core `workflows-shared` package, allowing workflow steps to access their attempt count via context, which can be utilized by workflow definitions for more robust execution logic.

This change affects Wrangler's workflow deployment process, introducing a new warning for users when deploying workflows that might belong to other workers. This new capability helps prevent accidental overwrites or conflicts by alerting users to potential issues before deployment.

This commit delivers **critical documentation fixes and updates** across the Workflows guides. It primarily **corrects and modernizes Python code examples**, updating them to use `workers` module imports, wrap API calls in `WorkerEntrypoint` classes, and correctly apply `await` for asynchronous operations within the `workflows/python` section. Additionally, it addresses a missing `useState` import in a React example for **Durable Agents** and resolves a typo and unused variable in the **reference limits** documentation. These comprehensive updates ensure the provided code snippets are accurate, runnable, and reflect current best practices, significantly **improving the clarity and reliability of the Workflows documentation** for developers.

This commit performs a **documentation update** to the **Workflows Python DAG documentation**. It **corrects example function names** within `src/content/docs/workflows/python/dag.mdx`, changing `step_a`, `step_b`, and `my_final_step` to `dep_1`, `dep_2`, and `final_step` respectively. This ensures the provided Python DAG examples are accurate and consistent, improving clarity for users learning about **Workflows** with Python.

This commit primarily **updates documentation** related to **Workers Vitest integration** and **Workflows**. It introduces new documentation for the `getOutput()` and `getError()` methods within the `WorkflowInstance` API, providing developers with clear examples for asserting Workflow results and errors in their tests. Additionally, the commit includes a minor **wording refinement** in the **Workflows reference documentation**, updating the 'Maximum queued Workflow executions' limit to 'Maximum Workflow executions' for improved clarity. This work enhances the developer experience by providing better guidance for testing Workflows and understanding system constraints.

This commit **updates the documentation** for **Workflows**, specifically correcting the stated maximum concurrent instances for free accounts. The `src/content/docs/workflows/reference/limits.mdx` file has been modified to reflect the accurate limit of 100, up from the previously documented 25. This **documentation fix** ensures users have the correct information regarding **free tier limitations**, preventing confusion and aligning the public-facing limits with the actual system capabilities.

This change introduces new testing utilities and a handler within `vitest-pool-workers` and `workflows-shared` to retrieve the results of workflow instances. This provides a new capability for developers to more effectively test Workflows, improving the reliability of workflow implementations.

This change affects the `create-cloudflare` package, introducing a new capability to automatically generate workflow names based on the worker name during project setup. This streamlines the configuration process for new Cloudflare Workers projects utilizing workflows.

This commit introduces a new `sendEvent` command to the `wrangler` CLI, providing a new capability for developers to interact with Workflows instances by sending events directly from the command line. This enhances the developer experience for managing and testing Workflows.

This commit **introduces a new capability** within the **Workflows** module by adding a **recommendation system for Static Assets**. This enhancement provides users with proactive suggestions and guidance specifically tailored to managing their static assets within the workflow environment. The work is a **feature addition** that aims to improve user experience and efficiency by offering relevant insights and best practices for asset utilization.

This commit **refactors** the **Workflows** module by removing an unnecessary `await` keyword from the codebase. The `await` was redundant as the operation it preceded was not truly asynchronous or its result was not being used in an awaited fashion, making it superfluous. This **maintenance** change improves code readability and slightly reduces overhead within the workflow execution logic, contributing to cleaner and potentially more efficient code.

[Workflows] Fix InstanceStatus types (#26808)