Cloudflare Workflows FAQs

Question 1

Can I wait for external events in a workflow?

Accepted Answer

Yes, using 'step.waitForEvent()', a workflow can pause execution until an external signal or webhook is received, with a configurable timeout of up to 30 days.

Question 2

How does state persistence work in this skill?

Accepted Answer

Workflows automatically persist any JSON-serializable data returned from a 'step.do()' call. This ensures that even if a workflow is paused or retried, the data from previous steps remains available.

Question 3

When should I use a NonRetryableError?

Accepted Answer

Use NonRetryableError for terminal failures where retrying will not help, such as invalid user input, authentication failures, or 404 errors for resources that will not be created.

Question 4

How do I test my workflows locally?

Accepted Answer

This skill supports testing via the 'cloudflare:test' module and Vitest, allowing you to mock step results, disable sleeps for faster tests, and introspect workflow instances.

Question 5

What is the primary benefit of Cloudflare Workflows?

Accepted Answer

Cloudflare Workflows allow you to build durable, multi-step processes that can run for hours or days with automatic state persistence, meaning they can survive restarts and handle long wait periods without manual intervention.

Cloudflare Workflows

Key Features

Use Cases

Cloudflare Workflows

Key Features

Use Cases