Limits

Execution limits

Checkpoints are capped at 16 MiB. Store larger data outside the Program and keep a reference in the continuation.

The Node adapter is the supported callback runtime on Node 22 and Node 24. Programs are TypeScript. There is no Python or Rust Pulse adapter. Callbacks are ordinary JavaScript. Pulse does not wrap them in a sandbox of its own.

Recovery guarantees

An effect whose result is in the committed journal is not dispatched again. An external effect can run again when its journal did not commit.

One process owns an execution at a time. A claim that loses the fence cannot commit. A second process does not commit under the same fence.

A deleted version stays waiting for the pinned artifact. Discovery does not move it onto another hash.

The dashboard reads the projection, not the checkpoint. situation is that projection’s label: terminal, owned, dormant, or recoverable. It can lag the checkpoint, so recoverable can appear while another process already holds the lease. It does not mean a compatible worker is connected, and it does not mean the next claim will succeed. The generation and the observed time on the page are from the projection read.

Operational responsibilities

You run the process. You deploy it, replace it, and keep a compatible artifact available for executions that are still pinned to it. Trigora does not provision the host.

Waiting wall-clock is free. Checkpoint bytes still occupy storage while the execution is suspended. Compute on your machines is not a Trigora charge.