Stuck? Fixes for common problems

Nothing happens at all

1. Is it published? The bot runs the live version only; a draft does nothing until you Publish.

2. Is its module on? A template's flows sit in their own module in the sidebar with one on/off dot. Built-in systems (Tickets, Moderation, Logs...) each have an Enabled switch on their page.

3. Any "Pick a channel" or "Pick a role" left? Those steps wait for your pick and are skipped until then. Publish lists them, and a template's Quick setup page asks for all of them at once.

4. Open Runs on the flow: every run is listed with the path it took, and a step that failed says why.

"That didn't work: ..."

Staff see the real reason when a step fails; members see a short sorry instead. The reason names the setting and what it needs, like a number from 1 to 100. Fix it in that step's side panel and Publish.

The bot can't give a role or time someone out

In Server Settings → Roles, drag the bot's role above every role it gives or takes. Discord never lets a bot manage a role above its own, or anyone with a higher role, or the owner.

Check the bot has the permission too: Manage Roles for roles, Moderate Members for timeouts, Manage Messages to delete, Manage Channels for tickets and threads.

Warn, timeout or ban does nothing

Those steps go through the Moderation system, so they're logged as cases. Turn Moderation on (its page, Enabled). Templates that use them turn it on for you.

A slash command doesn't show up

Commands appear once the flow is published. Discord can take a moment to show new ones: press Ctrl+R in Discord to reload. A staff command only shows for people with Manage Server.

A form or a button misbehaves

A form must be the first answer to a click or command: put Open form before any Reply or Wait. A button that says "This question was asked to someone else" belongs to another member's question.

Buttons in a DM work too; if a DM never arrives, that member has DMs from server members turned off. Steps like "DM or post" fall back to posting where it happened.

Text shows {var.something} or an empty name

A variable shows as-is until something sets it. Read it with Get variable and use its Found pin to say something else the first time. A typo in a {name} shows as-is too: pick names from the socket list instead of typing them.

Messages or text missing in logs

Edited and deleted text needs the bot's Message Content access and the message still being in its memory (sent since it last restarted). Joins, leaves, roles and nicknames need its Members access.

Still stuck?

Press Test and watch where the run stops: the step it stopped on says why. Each element's page (F1 on a selected node) says what every setting does and shows an example.