From 69a3d928ee1f7258cf9afa7024dfd44efbc79917 Mon Sep 17 00:00:00 2001 From: Alex Clarke Date: Thu, 10 Sep 2026 15:06:02 -0600 Subject: [PATCH] docs(graph): document max_loop_iterations: 0 in the example graph --- graph.example.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/graph.example.yaml b/graph.example.yaml index 9f31086..8901d99 100644 --- a/graph.example.yaml +++ b/graph.example.yaml @@ -116,7 +116,7 @@ variables: # --------------------------------------------------------------------------- settings: max_loop_iterations: 100 # Per-node visit cap. If one node id is entered more - # than this many times, execution aborts. Default 100. + # than this many times, execution aborts. Default 100; 0 = no cap. timeout: 600 # Optional wall-clock cap (seconds) on the whole run, # checked between node transitions. 0 = no bound. log_state_snapshots: true # Log state before each node (debug/trace). Default true. @@ -389,7 +389,7 @@ nodes: # Not supported inside a branch chain (validator errors): fan-out `next:` # lists, another `map`, `end`, `approval`, `input`. A branch node must not # also be reachable from `start` on the main flow. Per-item loops are script - # `_next` loops (bounded by settings.max_loop_iterations on the fork); a + # `_next` loops (bounded by settings.max_loop_iterations on the fork; `0` = unbounded); a # declared `next`/`fallback` edge back to an earlier chain node is a cycle. # # Reach via `synthesize`'s `_next: subjects_map`. The producer is expected