Repository navigation
docs(guides): add Cloudflare Workflows migration guide - #22
Draft
NathanFlurry wants to merge 2 commits into
Draft
NathanFlurry wants to merge 2 commits into
NathanFlurry wants to merge 2 commits into
Conversation
Map Cloudflare Workflows concepts to Rivet Workflows with before/after code: steps, retries and timeouts, CriticalError, tryStep, sleeps, join, starting workflows, status and terminate, and child workflows. The Rivet code lives in examples/docs/guides/migrate-cloudflare-workflows and is type-checked. Input and status use the workflow's SQLite database. step.waitForEvent and instance.sendEvent are documented as a current gap. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- onError skips attempts that will retry and the tryStep-handled send-receipt step, so a recovered failure no longer marks a running order failed; the complete step clears any stale error. - Explain that a step timeout does not cancel the callback, so retried timeouts need idempotent work. - Waiting for events: say plainly that event delivery currently uses queues, which are being deprecated, instead of promising a replacement. - The progress client connects with createWithInput before the first steps run and disposes the connection when done. - Rename the sidebar entry to "From Cloudflare Workflows" and soften the versioning comparison. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
7 of 11 tasks
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Migrate from Cloudflare Workflows guide at
/guides/migrate-cloudflare-workflows. It is listed in a new "Migrations" guides group, which merges with the actors bundle's group of the same name.WorkflowEntrypoint,event.payload,step.doandWorkflowStepConfig,NonRetryableErrortoCriticalError,try/catchtotryStep,sleep/sleepUntil,Promise.alltojoin, triggering through a Worker binding,status()/terminate(), and child workflows.examples/docs/guides/migrate-cloudflare-workflows/and passespnpm --filter @rivet-dev/workflows-docs-examples check-typesand biome.dbplusonCreate). The guide doesn't usestate, queues, or KV, which are deprecated or being deprecated in RivetKit.Gap:
step.waitForEvent/instance.sendEvent. Delivering a message to a running workflow currently goes through workflow queues (ctx.queue.*), which are being deprecated along with actor queues. The guide says so plainly and tells readers not to build new code on queues. It describes a polling workaround in prose, without code. Update that section once a replacement exists.Ported from rivet-dev/rivet#4389. That PR added the Cloudflare migration guides to the old website cookbook, before the docs moved into per-product bundles.
🤖 Generated with Claude Code