Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document the cascade guarantee and the cascade ceiling
Docs / docs (push) Successful in 22s
Details
Playwright Tests / test-playwright (1, 2) (push) Failing after 2m46s
Details
Playwright Tests / test-playwright (2, 2) (push) Failing after 1m42s
Details
pre-commit / pre-commit (push) Failing after 2m55s
Details
Test Backend / test-backend (push) Successful in 2m23s
Details
Compose Smoke Test / test-compose (push) Successful in 32s
Details
Playwright Tests / merge-reports (push) Failing after 1m3s
Details

Browse Source 
A node runs when something it reads was published, not merely when something
upstream of it ran — worth saying now that it is true, since it is what a
reader relies on when a rate-limited port goes quiet. Plus `FLOW_MAX_CASCADES`
in the engine's configuration table.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BpfSinyCBfjuieikyfMPbf
This commit is contained in:
stroblme
2026-08-26 10:27:23 +02:00
co-authored by Claude Opus 5
parent 1430c4060b
commit 266acd1661
2 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/configuration.md
+1
View File
@@ -123,6 +123,7 @@ warning into a refusal to start.
| Variable | Default | Notes |
|---|---|---|
| `FLOW_MAX_WORKERS` | `4` | node-code subprocesses run in parallel |
| `FLOW_MAX_CASCADES` | `4` | cascades in flight at once; throughput is this over the mean cascade time, so raise it where nodes wait on a network rather than a CPU |
| `FLOW_NODE_TIMEOUT` | `0` | seconds a node may be silent, unless it sets its own; 0 is no limit |
| `OBS_RETENTION_DAYS` | `30` | how long metrics, events and run records are kept |