cloudflare-workflows
Complete knowledge domain for Cloudflare Workflows - durable execution framework for building multi-step applications on Workers that automatically retry, persist state, and run for hours or days. Use when: creating long-running workflows, implementing retry logic, building event-driven processes, scheduling multi-step tasks, coordinating between APIs, or encountering "NonRetryableError", "I/O context", "workflow execution failed", "serialization error", or "WorkflowEvent not found" errors. Keywords: cloudflare workflows, workflows workers, durable execution, workflow step, WorkflowEntrypoint, step.do, step.sleep, workflow retries, NonRetryableError, workflow state, wrangler workflows, workflow events, long-running tasks, step.sleepUntil, step.waitForEvent, workflow bindings
What this skill does
# Cloudflare Workflows **Status**: Production Ready ✅ **Last Updated**: 2025-10-22 **Dependencies**: cloudflare-worker-base (for Worker setup) **Latest Versions**: [email protected], @cloudflare/[email protected] --- ## Quick Start (10 Minutes) ### 1. Create a Workflow Use the Cloudflare Workflows starter template: ```bash npm create cloudflare@latest my-workflow -- --template cloudflare/workflows-starter --git --deploy false cd my-workflow ``` **What you get:** - WorkflowEntrypoint class template - Worker to trigger workflows - Complete wrangler.jsonc configuration ### 2. Understand the Basic Structure **src/index.ts:** ```typescript import { WorkflowEntrypoint, WorkflowStep, WorkflowEvent } from 'cloudflare:workers'; type Env = { MY_WORKFLOW: Workflow; }; type Params = { userId: string; email: string; }; export class MyWorkflow extends WorkflowEntrypoint<Env, Params> { async run(event: WorkflowEvent<Params>, step: WorkflowStep) { // Access params from event.payload const { userId, email } = event.payload; // Step 1: Do some work const result = await step.do('process user', async () => { return { processed: true, userId }; }); // Step 2: Wait before next action await step.sleep('wait 1 hour', '1 hour'); // Step 3: Continue workflow await step.do('send email', async () => { // Send email logic return { sent: true, email }; }); // Optional: return final state return { completed: true, userId }; } } // Worker to trigger workflow export default { async fetch(req: Request, env: Env): Promise<Response> { // Create new workflow instance const instance = await env.MY_WORKFLOW.create({ params: { userId: '123', email: '[email protected]' } }); return Response.json({ id: instance.id, status: await instance.status() }); } }; ``` ### 3. Configure Wrangler **wrangler.jsonc:** ```jsonc { "name": "my-workflow", "main": "src/index.ts", "compatibility_date": "2025-10-22", "workflows": [ { "name": "my-workflow", "binding": "MY_WORKFLOW", "class_name": "MyWorkflow" } ] } ``` ### 4. Deploy and Test ```bash # Deploy workflow npm run deploy # Trigger workflow (visit in browser or curl) curl https://my-workflow.<subdomain>.workers.dev/ # View workflow instances npx wrangler workflows instances list my-workflow # Check instance status npx wrangler workflows instances describe my-workflow <instance-id> ``` --- ## WorkflowEntrypoint Class ### Extend WorkflowEntrypoint Every Workflow must extend `WorkflowEntrypoint` and implement a `run()` method: ```typescript export class MyWorkflow extends WorkflowEntrypoint<Env, Params> { async run(event: WorkflowEvent<Params>, step: WorkflowStep) { // Workflow steps here } } ``` **Type Parameters:** - `Env` - Environment bindings (KV, D1, R2, etc.) - `Params` - Type of workflow parameters passed via `event.payload` ### run() Method ```typescript async run( event: WorkflowEvent<Params>, step: WorkflowStep ): Promise<T | void> ``` **Parameters:** - `event` - Contains workflow metadata and payload - `step` - Provides step methods (do, sleep, sleepUntil, waitForEvent) **Returns:** - Optional return value (must be serializable) - Return value available via instance.status() **Example:** ```typescript export class OrderWorkflow extends WorkflowEntrypoint<Env, OrderParams> { async run(event: WorkflowEvent<OrderParams>, step: WorkflowStep) { const { orderId, customerId } = event.payload; // Access bindings via this.env const order = await this.env.DB.prepare( 'SELECT * FROM orders WHERE id = ?' ).bind(orderId).first(); const result = await step.do('process payment', async () => { // Payment processing return { paid: true, amount: order.total }; }); // Return final state return { orderId, status: 'completed', paidAmount: result.amount }; } } ``` --- ## Step Methods ### step.do() - Execute Work ```typescript step.do<T>( name: string, config?: WorkflowStepConfig, callback: () => Promise<T> ): Promise<T> ``` **OR** (config is optional): ```typescript step.do<T>( name: string, callback: () => Promise<T> ): Promise<T> ``` **Parameters:** - `name` - Step name (for observability) - `config` (optional) - Retry configuration - `callback` - Async function that does the work **Returns:** - The value returned from callback (must be serializable) **Example:** ```typescript // Simple step const files = await step.do('fetch files', async () => { const response = await fetch('https://api.example.com/files'); return await response.json(); }); // Step with retry config const result = await step.do( 'call payment API', { retries: { limit: 10, delay: '10 seconds', backoff: 'exponential' }, timeout: '5 minutes' }, async () => { const response = await fetch('https://payment-api.example.com/charge', { method: 'POST', body: JSON.stringify({ amount: 100 }) }); return await response.json(); } ); ``` **CRITICAL - Serialization:** - Return value must be JSON serializable - ✅ Allowed: string, number, boolean, Array, Object, null - ❌ Forbidden: Function, Symbol, circular references, undefined - Step will throw error if return value isn't serializable --- ### step.sleep() - Relative Sleep ```typescript step.sleep(name: string, duration: WorkflowDuration): Promise<void> ``` **Parameters:** - `name` - Step name - `duration` - Number (milliseconds) or human-readable string **Accepted units:** - `"second"` / `"seconds"` - `"minute"` / `"minutes"` - `"hour"` / `"hours"` - `"day"` / `"days"` - `"week"` / `"weeks"` - `"month"` / `"months"` - `"year"` / `"years"` **Examples:** ```typescript // Sleep for 5 minutes await step.sleep('wait 5 minutes', '5 minutes'); // Sleep for 1 hour await step.sleep('hourly delay', '1 hour'); // Sleep for 2 days await step.sleep('wait 2 days', '2 days'); // Sleep using milliseconds await step.sleep('wait 30 seconds', 30000); // Common pattern: schedule daily task await step.do('send daily report', async () => { // Send report }); await step.sleep('wait until tomorrow', '1 day'); // Workflow continues next day ``` **Priority:** - Workflows resuming from sleep take priority over new instances - Ensures older workflows complete before new ones start --- ### step.sleepUntil() - Sleep to Specific Date ```typescript step.sleepUntil( name: string, timestamp: Date | number ): Promise<void> ``` **Parameters:** - `name` - Step name - `timestamp` - Date object or UNIX timestamp (milliseconds) **Examples:** ```typescript // Sleep until specific date const launchDate = new Date('2025-12-25T00:00:00Z'); await step.sleepUntil('wait for launch', launchDate); // Sleep until UNIX timestamp const timestamp = Date.parse('24 Oct 2024 13:00:00 UTC'); await step.sleepUntil('wait until time', timestamp); // Sleep until next Monday 9am UTC const nextMonday = new Date(); nextMonday.setDate(nextMonday.getDate() + ((1 + 7 - nextMonday.getDay()) % 7 || 7)); nextMonday.setUTCHours(9, 0, 0, 0); await step.sleepUntil('wait until Monday 9am', nextMonday); // Schedule work at specific time await step.do('prepare campaign', async () => { // Prepare marketing campaign }); const campaignLaunch = new Date('2025-11-01T12:00:00Z'); await step.sleepUntil('wait for campaign launch', campaignLaunch); await step.do('launch campaign', async () => { // Launch campaign }); ``` --- ### step.waitForEvent() - Wait for External Event ```typescript step.waitForEvent<T>( name: string, options: { type: string; timeout?: string | number } ): Promise<T> ``` **Parameters:** - `name` - Step name - `options.type` - Event type to match - `options.timeout` (optional) - Max wait time (default: 24 hours) **Returns:** - The event payload sent via `instance.sendEvent()` **Example:** ```typescript ex
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.