Skip to content

Caching and concurrency

Orvanta gives you two levers to control cost and load: caching to avoid redundant work, and concurrency limits to cap how many jobs run at once.

Caching

A node can cache its result for a configurable duration. While the cache is valid, repeated executions with the same inputs return the stored result instead of re-running — useful for expensive or rate-limited operations.

Concurrency limits

A concurrency limit caps the number of simultaneous executions for a script, workflow, or custom key. Excess runs queue until a slot frees up, protecting downstream APIs and databases from overload.

Error handling — Retries and backoff for rate-limited calls.
Jobs and runs — How queued executions are tracked.