Build
Run parameters and replays
A project can declare run parameters in exuvia.json. A node that reads
one says so, and its output is then stored once per value:
{
"name": "put-selling",
"timezone": "America/New_York",
"params": { "as_of": { "type": "date", "default": "today", "description": "Run date" } },
"schedules": { "screen": "30 16 * * 1-5" }
}@exuvia.node(params=["as_of"])
def screen():
day = exuvia.param("as_of") # "2026-11-06": dates arrive as ISO strings
...-- params: as_of
select * from screen where as_of_date <= $as_of- Types are
date,string,numberandboolean. Adatedefault oftodayresolves to the run date in the projecttimezone. - One output per parameter set. Running for
as_of=2026-11-06does not overwrite today's output; running it again is a cache hit. A node that declares no parameter and reads none upstream is computed once and shared. - Replays.
POST /api/backfillruns the graph for each value in a list or date range (weekdays only by default), skipping values that are already fresh. Progress is onGET /api/backfilland the event stream. - Time series for free. In
query_dataandPOST /api/query,<node>__runsunions a node's output across every parameter set that has run, with a_<param>column each (select _as_of, count(*) from screen__runs group by 1). timezonealso sets the clock for cron schedules.schedulesoverrides or adds a per-node cron without editing the node file (this is what the schedule API writes), so an embedding app can let people schedule nodes.
exuvia run my-project --param as_of=2026-11-06
exuvia status my-project --param as_of=2026-11-06