Troubleshooting

Nothing happens#

• Is the workflow Live? Paused workflows never run. Enable is greyed out while there are unsaved changes.
• Did you wait up to 30 s after saving? The bot caches enabled workflows.
• Does the trigger filter match? Message sent with a channel filter ignores every other channel; Slash command used compares the bare command name without the slash.
• Was the event caused by a bot? Message, member and reaction triggers ignore bot accounts and webhooks.
• Hit the rate limit? More than 30 runs of one workflow within a minute are skipped (a warning is logged to the bot's system channel).

The editor refuses to save#

Read the toast — it names the block and the problem. Common ones:

“… needs a channel, but the trigger … doesn't provide one”

The trigger has no channel context (role change, join, schedule…). Pick a channel in the action's settings.

“… needs a message …”

Reply / react / pin / delete only make sense after a message or reaction trigger.

“Add at least one trigger block”

Every workflow needs a trigger to start from.

“Role is required” / “Select a valid role”

A required picker is empty, or the role/channel no longer exists on the server.

“… invalid regular expression”

The pattern in Text matches? (regex mode) does not compile.

An amber “Last run failed” strip appears#

The run reached an action that could not complete. The message is the bot's own explanation:

Cannot manage role @X — check the bot's role position

Move the PaulCLI role above @X in Server Settings → Roles.

Cannot timeout / kick / ban … — role hierarchy

The target's highest role is at or above the bot's.

Channel not found — it may have been deleted

Re-select the channel in the block.

Missing Permissions

Grant the permission the action needs (see Bot permissions).

Step limit (50) exceeded — check for loops

Your graph loops back on itself. Add a Stop or a condition that breaks the cycle.

Run exceeded its time budget

Too many Wait blocks in sequence; keep total waiting under ~80 s.

Schedules fire late or twice#

The scheduler ticks once a minute. Every N minutes starts counting from when the bot first sees the workflow enabled, and Daily at HH:MM fires once in that minute. After a bot restart the first interval is re-baselined, so a 60-minute schedule may run up to 60 minutes after the restart.