backend-workflows

Durable backend workflows use step-based orchestration with checkpoints and idempotent steps, so long-running operations recover cleanly and retry with controlled backoff if any step fails. You structure processes with clear execution flow and durable state.

Progress tracking in durable workflows uses reportProgress during step execution, allowing you to start, inspect, and wait on workflow runs while reporting meaningful progress updates for long-running operations like data imports or validation.

Scheduled automation implements cron-based or time-driven jobs for nightly, periodic, or maintenance tasks using BaseScheduledWorkflow. These durable workflows support retry-safe steps with delayed backoff for reliable unattended execution.

Durable workflows are needed for long-running, failure-prone operations like multi-stage data imports that require retries, checkpoints, progress tracking, and clean recovery. Standard processing lacks the orchestration and durability for these scenarios.

Yes, durable workflows require idempotent step design with controlled retries and delayed backoff. Each step uses durable checkpoints so re-execution after failure produces consistent results without duplicating side effects.

Workflow orchestration structures multi-step backend processes using @Workflow, @Step, and callStep to define execution flow with durable checkpoints. WorkflowsManager handles queue selection, execution monitoring, and progress reporting across all steps.