Developing workflows on your own machine
Why a durable job engine needs a local mode, what running one on your own machine lets you test, and how to test multi-step logic without one on Voroa.
What this covers
Testing a workflow against a hosted engine is slow, because every change means a deploy and every failure case means waiting for a real retry. That is why workflow platforms ship a local mode: the engine runs on your own machine, executes your steps against your local services, and lets you force a step to fail so you can watch the retry behave. It turns a category of bug that is otherwise only reproducible in production into something you can step through in a debugger.
Workflows are not available on Voroa today, so there is nothing to run locally. Multi-step logic inside a background worker can be tested the ordinary way, by running the worker’s code directly on your machine before you deploy it.