Durable engine
Durable engine
The durable engine keeps long work going across restarts and deploys. When a piece of work takes longer than one sitting, such as a chain of steps, it is saved step by step. If the server process running it stops, another process carries on the unfinished runs. A step that might have spent money, such as a purchase, is not done twice: the process that carries on asks whether it happened. The module is called Durable runs.
In the sidebar under Admin → Durable engine.
Durable engine screen
Which server processes are running durable work, when each was last heard from, and whether one stopped and had its unfinished runs carried on by another.
- A process silent for two minutes is treated as stopped.
- A live process's work is never taken from it.
Nothing here is a workspace's data. The runs themselves are on the Chains page.
Who can do what
| Permission | What it lets you do |
|---|---|
durable:read — See the durable engine and which server processes run durable work | Open this screen. |
What happens on its own
| Job | When | What it does |
|---|---|---|
recover | Every minute | Finds processes that stopped and hands their unfinished runs to a live one. |
Needs
Nothing else switched on.
What agents can do
Nothing. This module gives agents no tools.