Workflows
A workflow is the core unit of automation in Hakona. It defines a sequence of steps that runs automatically whenever a trigger condition is met.
Anatomy of a workflow
Every workflow has three parts:
- Trigger — The event that starts the workflow. A workflow has exactly one trigger.
- Steps — One or more actions, conditions, or loops that execute in order.
- Runs — Each time the trigger fires, Hakona creates a new run that executes all steps.
Workflow states
| State | Meaning |
|---|---|
| Draft | The workflow has never been deployed. Changes are saved but it won't run. |
| Active | The workflow is deployed and will execute when the trigger fires. |
| Paused | The workflow is temporarily stopped. Triggers are ignored until you resume it. |
| Error | The last run failed. The workflow will continue running for future triggers. |
Execution model
Hakona executes workflows deterministically — each step runs exactly as configured, in order, with no AI inference between steps. This makes workflows predictable, auditable, and safe to run in production.
If a step fails, Hakona retries it according to the retry policy you configure (default: 3 retries with exponential back-off). If all retries fail, the run is marked as failed and you receive an alert.
Versioning
Every deployment creates a new version. You can view the history of all deployed versions and roll back to a previous one at any time from Workflow → History.