Temporal Execution Engine
Run Revo workflows on a durable execution engine built on Temporal, with step level checkpointing, automatic retries, full history, and local fallback.
Revo runs workflows on a durable execution engine built on Temporal. Workflows survive crashes without losing their place, recover from transient failures with automatic retries, keep a full execution history, scale horizontally, and fall back to local execution when the durable engine is unreachable.
How it works
The engine captures workflow state after every step rather than only at the end. If the host running a workflow crashes, restarts, or loses power, a healthy host picks up the workflow from the last completed step and continues, losing at most the single step that was in flight. Transient failures such as a service that briefly stops responding, a network blip, or a rate limit retry automatically with backoff. Every run keeps a complete record that can be searched, exported, and replayed.
Key capabilities
- Durable execution on Temporal, with state captured after every completed step.
- Step level checkpointing and automatic resume on a healthy host after a crash.
- Automatic retries with exponential backoff, tunable per step, integration, or workflow, with controls for attempts, elapsed time, initial backoff, growth rate, and which error categories retry versus fail fast.
- Full execution history capturing the trigger, every step, inputs, outputs, timing, retries, decisions, and final result, retained for the workspace lifetime.
- Horizontal scaling, since workflow state lives in a durable store independent of any host.
- Graceful local fallback that keeps work moving and history complete when the durable engine is temporarily unreachable, switching back automatically on the next step.
Tips
Replay reconstructs a previous run from captured inputs and recorded decisions, which is useful for deterministic debugging. Re running fires a new workflow with the same inputs but against current state, which is useful for testing changes. Both are one click in the execution history view.