ReferenceAutomations
Validation
Publish validation codes and runtime limits for automations.
Publish runs full graph validation. Issues are returned with a code and message, and badged on affected nodes in the editor.
Validation codes
| Code | Meaning |
|---|---|
no-trigger | The graph has no trigger node. |
multiple-triggers | More than one trigger is present. |
unknown-node-type | A node type is not recognized. |
unknown-edge-endpoint | An edge points to a deleted node. |
unknown-socket | An edge uses an invalid socket name. |
invalid-flow-port | A flow wire targets a branch that does not exist. |
flow-into-pure-node | A flow wire connects to a value node. |
duplicate-flow-source | One flow output connects to multiple targets. |
duplicate-input | One input socket is wired more than once. |
type-mismatch | Connected sockets have incompatible types. |
missing-required-input | A required data socket is unwired. |
invalid-static-value | A literal or static config value is invalid. |
invalid-config | Node configuration fails schema validation. |
flow-cycle | Flow wires loop back on themselves. |
data-cycle | Data wires form a dependency loop. |
for-each-output-without-array | For Each has no array wired. |
for-each-output-outside-loop | Item or Index is used outside the Each branch. |
for-each-nesting-too-deep | Nested For Each loops exceed the nesting limit. |
step-budget-exceeded | Worst-case flow steps exceed the step budget. |
Runtime limits
| Limit | Value |
|---|---|
| Flow steps per run | 500 |
| Pure node evaluations | 1500 |
| For Each nesting depth | 3 |
| Max delay | 28 days |
| Automations per guild | 100 |
| Nodes per automation | 100 |
| Metadata entries per send | 8 |
| Max array length | 20 |
How is this guide?