How a graph runs

A graph belongs to the server it was built on.
A server can have any number of graphs.

A graph fires only while it is switched on.
A new graph starts off.
run works on a graph that is off.

Time triggers check the clock once a minute.
They fire whether or not the server is running.
Event triggers fire when their own server reports the event.
Event triggers wait out their Cooldown (seconds) between firings.

Graphs run only while Konnekt is open.
Closing Konnekt stops the scheduler, and stops a running server too.
A time that passes while it is closed is not made up.

Control wires set the order.
Each block leaves by one control port, such as onComplete or onTrue.
Only the blocks wired to that port run next.
Blocks wired to the same port run one after another, in an order not to rely on.
Chain them with a wire when the order matters.
A block that no control wire reaches never runs.

Data wires carry values.
A wired value replaces the block's own field.
A wire that has no value yet leaves the field in use.

Blocks with no control ports, such as Read Attribute, Constant and Math, run when a block that needs their value runs.
They run once per run, and every block wired to them gets that value.
The outputs of other blocks, such as the Backup filename of Create Backup, exist once that block has run.
A block wired to one that has not run yet reads nothing.

A block that fails leaves by onFailed.
The blocks wired there run, so a graph can handle its own failure.
With nothing wired there, that branch ends and the other branches carry on.
The run is marked failed either way, with the reason of the first failure.

A failed run raises a Run failed bubble with the reason and adds it to Notifications.
It also writes the reason to the server's console, unless the block already did.

A graph runs once at a time.
A trigger that fires during a run starts nothing, and is not queued.
Different graphs run at the same time.

A block is cut off after 60 s, except the upload and Distant Horizons blocks, which have longer limits.
A run is cut off after 30 minutes, or longer when its blocks have longer limits.
A run also stops after 500 block executions, which ends a loop.