Node reference

The shape every flow has — an entry, the decisions, the model call and the answer — and a table of every node of the builder.

A port is a named exit of a node. Which ports must be connected, and what happens when a node leaves through one that is not.

The three roots a node reads data from, how a path is written, what each node leaves for the nodes after it, and what happens when a path finds nothing.

Which node of a flow really moves the money of a model call, what the four nodes of the money chain add, and the order the publish check asks of them.

Which nodes put an execution down, what the request is answered with, what money is held during the wait, and how and when the execution goes on.

The checks of the graph and of the settings of each node, which of them stop a publication, and the message the builder shows for each.

The entry node of a flow — where a request comes in and hands its input to the next node.

A node of the money chain that writes into the trace what the model call it leads to is expected to cost.

A node that asks whether the model call ahead fits the policies, the budgets and, if you set one, the node's own allocation — and branches before any money is held.

A mark in the money chain that shows where the hold of the model call ahead is taken — the hold itself is taken by the model node.

A mark after a model call that shows where its hold is settled — Slen settles the hold itself, with or without the node.

A node that stops an execution until a person approves or rejects it, and sends it on along the branch of the decision.

A node that compares one value of the execution with a value you set and sends the flow down one of two branches.

A node that writes a line of your own into the trace of the execution, with values of the execution filled in.

A node that builds one object out of values of the execution and fixed values, for the nodes after it and for the answer.

A node that looks for a stored answer to the same request and, when it finds one, lets the flow answer without calling the model.

A node that stores the answer of the model under the key a lookup in the cache above it missed, so that the same request is answered from the cache next time.

The node that calls a model — it holds the money of the call, sends the call through a provider pool and has the hold settled after the answer.

A mark on the path a flow takes when its first choice is refused or fails — the other way is the nodes behind it.

The terminal node that ends an execution as completed and answers the caller — with what the model said, the input, a fixed object or the output of a node.

The terminal node that ends an execution as rejected, with an error code and a message its author chose.

A node that makes an execution wait a set number of seconds and then lets it carry on.

A frozen node that calls an HTTPS address on the allowlist of the service and branches on the answer, in the versions published with it.