Test mode
Test mode runs your draft on your real Discord server, but only for testers. Every other member keeps using the deployed version. You see each execution live, node by node, and you can undo what the test did.
Testers
A tester is a role or a member whose line allows Tester, on the server's Team page (Team and permissions). Starting a session takes the Run tests permission. During a session, what they do on Discord (a command, a message, joining) triggers the draft; for everyone else, nothing changes.
- Neither the owner nor the managers are testers by default, and @everyone doesn't give it: turn it on for yourself on the Team page, on the Server owner or Server managers line. Another member gets it from a manager (Tester).
- A Discord ID lets you add someone who hasn't joined the server yet, to test "Member Added" with a second account.
- Some Events have no direct author: a channel created, a role edited, a member banned. The bot finds who did it in the server's audit log, which takes the Discord permission View Audit Log. Without it, or if the author isn't a tester, the deployed version runs. The start window warns you.
Starting a session
Test, in the editor's top bar, opens the start window; the draft is saved when the session starts. You need to hold the edit lock on the Blueprint and the permission to edit.
| Setting | Choice |
|---|---|
| Scope | Every Event of the Blueprint, or one only |
| Repetition | Once per Event, then the session stops; or unlimited, until stopped |
| Undo reversible actions at the end | Revert what the test did on Discord when the session ends |
| Step through, one node at a time | A pause after each node, for one Event, once |
The window points out what needs attention: moderation Actions on real members, what undo won't be able to revert. With no tester at all, it only offers to open Team; once Tester is given, “Back to the test”, at the top of Team, brings you back to this window.
During the session
- The draft is frozen as it was at the start, and the Blueprint is locked for editing, for everyone.
- The deployed version steps aside for testers on the Events in scope: a tester only triggers the draft, never both.
- Test commands: a command of the draft is registered on Discord under a suffixed name,
/ticket-test, for the length of the session. The Test section gives you the name to type, to copy in one click. - 20 minutes at most, one session at a time per Blueprint. Stop test ends it sooner.
The Test section shows each execution as soon as it starts: the Event, the outcome, the duration. Click an execution to read, on the right, each node's trace with what it produced. In the Executions section, a test execution also shows on the canvas, like any other.
Node by node
When stepping through, the execution pauses after each node, the Event included. Look at what it produced, then click Next. Without a click for 90 seconds, it moves one node forward and pauses again. The 30-second limit of an execution doesn't apply.
Waits and scheduled Events
- A Wait sets its branch aside as in production. Skip the wait resumes it right away.
- A Scheduled Event of the draft never fires on its own during the session: Run now starts it. The deployed version's one keeps running normally.
The end, and undo
The session ends when you stop it, after 20 minutes, when every Event in scope has fired (with "once" repetition), or if you close the editor. Test commands are removed from Discord, and the deployed version takes over again for testers.
If you chose undo, the bot reverts what the test did, newest first, and the Test section shows the result:
| Actions | |
|---|---|
| Undone | Messages sent or edited, channels, categories and threads created or edited, reactions, roles, timeouts, server and member Variables |
| Partly | A banned member is unbanned, but not added back to the server |
| Never | Deleted messages, deleted channels and categories, kicked members, modals shown |
A reply only its recipient can see (ephemeral) can't be removed.
What's left afterwards
Each session is kept 14 days in the Executions section's Test sessions tab, with its executions and the undo result. Its executions also appear in the Executions section, filterable by source (test), and the Blueprint's activity log keeps one line per session.
Test executions count toward the server's rate limits, but not toward analytics.