Skip to main content

Crate openquiver_runtime

Crate openquiver_runtime 

Source
Expand description

Running a workflow, durably.

A run’s state is its journal. Nothing is held anywhere else: every node writes what it is about to do before doing it, and what it produced afterwards, and resuming is a walk over those records back to the position the run was in. That inverts the usual role of a log — here it is the authority rather than a commentary — and it is what lets a run outlive the process, the terminal and the machine’s next reboot.

Long waits are the normal case rather than the exception. An agent turn takes minutes, an approval can take days, and a run that dies with its window would be useless for either.

Structs§

Runtime
One run in progress.

Enums§

InDoubt
What to do about a node that was entered but never left.
JournalError
A journal entry that could not be understood.
Progress
What one step of a run did.
RunValue
A value on its way from one pin to another.
RuntimeError