You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 931f02a
Browse filesBrowse the repository at this point in the historyBrowse files
docs(skills): the formula skill and the flows page teach the null-guard gate on a record-triggered flow's conditions
The publish-time null-guard gate judges a record-triggered flow's start
`config.condition`, every edge `condition` (nested regions too) and every
`decision` branch `expression`. The formula skill now teaches which slots
are judged, the `count` / `sum` roll-up exception, the bare-name rule, the
start-condition guard spelled `record.<field> != null` so both doors
accept it, and the run-fails outcome; one eval exercises a refused flow
edge. The flows page carries the same rule where edge and decision
conditions are taught. Paid in the same file: the `previous` callout
restating §5 and the pre-ADR-0032 history clause.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WGufzfSZ55f7xwAfpfkPgY
docs(skills): the formula skill teaches the null-guard gate on a record-triggered flow's conditions
6
+
7
+
Clause-②: no
8
+
Metadata-protocol: none
9
+
10
+
The publish-time null-guard gate (`os validate` / `os build` / `os lint` and the runtime publish gate) has judged a record-triggered flow's start `config.condition`, every edge `condition` and every `decision` branch `expression` since the lint change that widened it; the formula skill now says so where it teaches the gate: which slots are judged, that a `count` / `sum` roll-up is always valued while `min` / `max` / `avg` stay nullable, that a bare field name in a flow condition is the field and is judged alike, that a guard in the start condition holds at every edge and branch and is spelled `record.<field> != null` so both doors accept it, and that an unguarded null fails the run while the write that fired it still lands. One eval exercises a refused flow edge. The flows docs page carries the same rule where edge and decision conditions are taught.
Copy file name to clipboardExpand all lines: content/docs/automation/flows.mdx
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1810,7 +1810,7 @@ Edges connect nodes and define the execution path:
1810
1810
|`source`|`string`| ✅ | Source node ID |
1811
1811
|`target`|`string`| ✅ | Target node ID |
1812
1812
|`type`|`enum`| optional |`'default'` (success), `'fault'` (error), `'conditional'` (expression-guarded), or `'back'` (declared back-edge, ADR-0044); defaults to `'default'`|
1813
-
|`condition`|`string`| optional | Boolean CEL predicate for branching (a bare string is stored as `{ dialect: 'cel', source }`) |
1813
+
|`condition`|`string`| optional | Boolean CEL predicate for branching (a bare string is stored as `{ dialect: 'cel', source }`); on a record-triggered flow a nullable field needs its `!= null` guard — see [Expressions in flows](#expressions-in-flows)|
1814
1814
|`label`|`string`| optional | Label displayed on the connector — cosmetic only. It does **not** select a path except on a branching node (`decision` / `approval`), which picks its out-edge by label. |
1815
1815
|`isDefault`|`boolean`| optional | BPMN default flow — the **"otherwise" branch**. Traversed only when no sibling `condition` on the same source node matched; never part of the unconditional parallel fan-out. Mutually exclusive with `condition`, at most one per node |
1816
1816
@@ -2443,6 +2443,18 @@ and is read as `vars["current_user"]` / `vars["vars"]`.
2443
2443
4.**A single-brace token in a text slot** — `title: 'Deal won: {record.name}'`
2444
2444
— is refused with its `{{ }}` spelling ([text slots](#text-slots-read-double-brace-holes)): it is no placeholder there,
2445
2445
and would go out as literal text.
2446
+
5.**An ordering or arithmetic operator on a nullable field, unguarded** — on a
2447
+
record-triggered flow (`triggerType: 'record-*'`), `os validate` and the
2448
+
runtime publish gate refuse a start `condition`, an edge `condition` (nested
2449
+
regions too) or a `decision` branch `expression` that applies `< <= > >=` or
2450
+
`+ - * / %` to a field of the trigger object with no `required: true`,
2451
+
`defaultValue` or default option (a `count` / `sum` roll-up reads `0` when
"prompt": "A record-change flow on `project` (start `triggerType: 'record-after-update'`, `objectName: 'project'`) escalates when the budget passes 200000. `budget` is a currency field with no `required` and no `defaultValue`. Write the edge condition from the decision node to the escalation branch.",
87
+
"expected_output": "`record.budget != null && record.budget > 200000`. The run binds every declared field of the trigger record, `null` when empty, and CEL has no `>` overload for null, so `os validate` and the runtime publish gate refuse the unguarded edge; at runtime the run would fail at that edge while the write that fired it still lands. A bare `budget > 200000` is the same field and is refused the same way, and `has(record.budget)` is not a guard: a declared field holding null is still present.",
0 commit comments