Merge remote-tracking branch 'origin/main' into HEAD

docs/code/cli.md

@@ -151,7 +151,8 @@ Client commands use the nearest `.fluksio/client.json`, or the global
 configuration when there is no project instance. Legacy client configuration
 is a fallback.
 `FLUKSIO_URL` and `FLUKSIO_TOKEN` override saved values; command options
-`--url` and `--token` override both.
+`--url` and `--token` override both. An engine URL works with or without
+the `/api/v1` path.
 
 A client needs an engine at least as new as itself. An engine from before
 flow ids cannot create flows the way this client does, and the client says

docs/concepts/runs.md

@@ -18,9 +18,17 @@ A batch flow does not need activation and does not open subscriptions,
 schedules or webhooks. A run executes each node once after its dependencies
 finish. Missing parameters use their declared initial values.
 
+When a node fails, the nodes that wait on it are recorded as `skipped` and
+the run ends `error`. A node that cannot be loaded fails the run before
+anything executes, with the node's load error as the reason.
+A node with no value on a triggering input fails without being called, as a
+live flow would wait for it, so a canvas port with a default needs
+`trigger: false` to be optional.
+
 Non-streaming ports cannot use `interval` in a batch flow: there is no timer
-to deliver a delayed value. Streaming ports can use it to reduce display
-updates while keeping every metric point.
+to deliver a delayed value. The same goes for a delay node's `interval`
+setting. Streaming ports can use it to reduce display updates while keeping
+every metric point.
 
 ## Submitting
 

docs/interface/dashboards.md

@@ -188,6 +188,21 @@ Choose the chart's data source:
 
 Multi-line charts show a legend as well as different colours.
 
+A Query chart offers 1h, 6h, 24h and 7d down its right-hand edge, and opens on
+24h. Under **Ranges** you can give it windows of its own instead, up to eight,
+and it opens on the one its `range_s` names or else the first. Each window
+becomes the request's `range_s` and `interval_s` when picked. A `range_s` of
+`0` asks for the whole history, and the answering flow decides how far back
+that reaches.
+
+```json
+"ranges": [
+  {"label": "1M", "range_s": 2592000, "interval_s": 86400},
+  {"label": "1Y", "range_s": 31536000, "interval_s": 86400},
+  {"label": "All", "range_s": 0, "interval_s": 86400}
+]
+```
+
 !!! tip "Skip the unfinished bucket"
 
     If your query aggregates into time buckets, leave out the bucket still