Introduction to workflows: durable multi-step jobs
What a workflow engine does that a plain background job cannot, why saved state between steps matters, and where this fits alongside workers and cron.
What this covers
A workflow is a job made of steps that has to survive a failure in the middle without repeating work it already did. The engine records the outcome of every step, so when something fails and the job is retried, it resumes from the failed step rather than starting over. That property, usually called durability, is what makes workflows suitable for anything involving money, external providers or anything else you cannot afford to run twice. It is also why a workflow is different from a background worker, which simply runs code, and from a scheduled task, which simply runs on a timer.
Workflows are not available on Voroa today. For work that can safely start over, a background worker or a scheduled task may be enough.