Running, caches and partial runs
Catenivo executes the active graph and then publishes destinations whose outputs could be prepared and validated.
Run a workflow
Use Run to start the project. The run dialog displays required parameters and any confirmations for destructive operations.
The journal distinguishes information, warnings, errors, reads, writes and rejected features. A completed run may still contain rejects: review the counters and Rejected branches.
Enable caching
Caching retains workflow outputs so you can:
- inspect produced features;
- display values in the inspector;
- reuse a compatible result during a partial run.
A cache is not a permanent copy of source data. Its validity depends on the graph, parameters, sources and the engine identity that produced it.
Fresh or stale cache
A functional upstream change invalidates affected caches. Cosmetic changes—position, display label or canvas layout—should not make a cache stale.
A complete empty cache is valid: zero features is not the same as “no cache”.
Run until here
A component’s context menu provides Run until here. Catenivo executes required dependencies up to and including the selected component, without executing its descendants.
This is useful for preparing or inspecting an intermediate point before writing destinations.
Run from here
Run from here recalculates the selected component and its descendants. Inputs entering the selected scope from outside must have complete compatible caches.
Catenivo does not silently reread missing sources to complete that boundary. If a required cache is missing or stale, the run is refused with a diagnostic.
Inspect data
Click an output cache indicator to open the data table. Compatible geometries can also be displayed on the map.
Caches can contain sensitive data and should be protected with the same access rules as the source data.
See also Project parameters and Loops and subprojects.