Recovering a failed process
When a step fails, the instance stops and an incident is raised. Here are the ways to get it moving again.
In short
- 01
A failed instance is paused, not lost — its data is kept.
- 02
Retry, skip the step, or restart from a different step.
- 03
Every recovery action is recorded in the instance history.
Things fail: a service is down, a worker has a bug, a variable is missing. Orkovia does not throw the instance away. It marks it failed, raises an incident with the error message, and waits for you.
Your options
| Action | What it does | Use it when |
|---|---|---|
| Retry | Runs the failed step again from scratch | The cause was temporary, such as an outage |
| Skip node | Moves past the failed step without running it | The work was already done some other way |
| Restart from node | Continues from a step you choose, keeping the variables | You need to go around a broken step |
| Edit variables and retry | Changes variables, then retries, in one call | Bad input data caused the failure |
| Roll back | Restores variables to an earlier point in the history, then retries | A step wrote wrong data before failing |
Moving a healthy instance
Sometimes nothing has failed, but an instance is waiting in the wrong place. Move token takes a waiting token from one step and puts it on another, without needing an incident. Any pending job or task at the old step is cancelled, so it cannot be completed later by mistake.
Fixing many at once
If one outage caused a hundred incidents, use a batch operation to resolve them together. The batch reports success or failure per item, so one stubborn instance does not block the rest.
See it on your own process
Book a walkthrough with the Orkovia team.
Keep reading
Upgrading running processes: migration and batch operations
Move live instances onto a new version of a process, and cancel, retry or update many instances in one go.
Read articleWho did what: the audit log and execution history
Two records answer two different questions: what happened inside a process, and who changed something in the platform.
Read articleDecision tables with DMN and FEEL
Move business rules out of code and into a table anyone can read: build a discount table, test it, and call it from a process.
Read article