Automations
Publishing
Drafts, publish validation, runtime limits, and troubleshooting failed publishes.
Automations have two versions: a draft you edit in the library and a published version the bot runs. Saving a draft never affects live behavior.
Draft vs publish
| Action | Effect |
|---|---|
| Save draft | Stores the current graph. Always allowed if the graph is well-formed. |
| Publish | Validates the full graph and updates the live automation the bot indexes. |
If publish fails, Assistance badges the affected nodes in the editor and lists every issue. Fix them, then publish again.
Structural validation
| Issue | What it means |
|---|---|
no-trigger | The graph has no trigger |
multiple-triggers | More than one trigger is wired |
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 input or output 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 config value is invalid |
invalid-config | Node configuration fails 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 used outside the Each branch |
for-each-nesting-too-deep | Nested loops exceed the nesting limit |
step-budget-exceeded | Worst-case steps exceed the step budget |
Runtime limits
| Limit | Value |
|---|---|
| Flow steps per run | 500 |
| Pure node evaluations | 1,500 |
| For Each nesting depth | 3 |
| Max delay | 28 days |
| Automations per guild | 50 |
Node-specific rules
- Compose Template must pass the full template schema before publish
- Make Button and Make Select Option require a label and action
- Command Executed option names must be unique; the command that runs the automation owns the slash command name
- Reply to Interaction, Follow Up, and Edit Interaction Response need a Template. Follow Up also needs an Interaction or Response input.
- Emoji literals must resolve to a valid emoji
- Paginated fetchers accept limits of 0–20 and pages ≥ 1
Tips for a clean publish
- Start with one trigger and one action — publish early to confirm the event fires
- Wire required inputs before adding branches
- Keep For Each Item/Index inside the Each branch
- Use Filter instead of If when you only need to skip, not branch
- Check step budget on complex graphs with nested loops
Related
How is this guide?