Workflows, Workers - All Wrangler commands for Workflows now support local development

All wrangler workflows commands now accept a --local flag to target a Workflow running in a local wrangler dev session instead of the production API. You can now manage the full Workflow lifecycle locally, including triggering Workflows, listing instances, pausing, resuming, restarting, terminating, and sending events: npx wrangler workflows list --local npx wrangler workflows trigger my-workflow --local npx wrangler workflows instances list my-workflow --local npx wrangler workflows instances pause my-workflow --local npx wrangler workflows instances send-event my-workflow --type my-event --local All commands also accept --port to target a specific wrangler dev session (defaults to 8787 ). For more information, refer to Workflows local development .

Workflows, Workers - All Wrangler commands for Workflows now support local development

Source

You might also wanna read

Cloudflare expands AI bot management tools with granular traffic controls for all customers

Workers - Simpler runtime types with @cloudflare/workers-types v5

AI Search - Manage AI Search sync jobs with Wrangler CLI

Workers - Work across multiple accounts with Wrangler auth profiles

Cache - Cache multiple versions of a URL with Vary

Cloudflare One - Hostname routing for Cloudflare Mesh

Comments