Server vs Local Execution
Canvas workflows can run in two modes: local execution (in your browser) and server execution (on the Otesse backend). Understanding the difference helps you choose the right mode for each workflow.
Local Execution
When you click Play in the canvas editor, the workflow runs locally in your browser by default. This is the mode used during development and testing.
Best for:
- Building and testing new workflows.
- Debugging step configurations.
- Quick one-off runs where you want to see results immediately.
Limitations:
- Stops if you close the browser tab.
- Cannot run on a schedule.
- Performance depends on your browser and internet connection.
Server Execution
Server execution runs your workflow on the Otesse backend using durable execution. This means the workflow runs reliably even if you close your browser, lose internet, or your computer shuts down.
Best for:
- Scheduled workflows that need to run automatically.
- Long-running workflows with multiple delays.
- Production workflows that must complete reliably.
- Workflows triggered by webhooks from external systems.
How it works:
- The server processes each step sequentially, saving progress after each one.
- If a step fails, the server can retry it based on your error handling configuration.
- Results are stored and available in the Execution History panel when you return.
Choosing a Mode
| Scenario | Recommended Mode |
|---|---|
| Building and testing | Local |
| Scheduled daily reports | Server |
| Webhook-triggered flows | Server |
| Quick data lookups | Local |
| Multi-day delay workflows | Server |
Tips
- Always test locally first, then switch to server execution for production.
- Server execution uses your saved canvas version — make sure to save (Ctrl + S) before activating.
On this page