Recovery

Find your problem

Payment confirmation pending? Refresh the activation page and do not pay again. For duplicate payments, restricted access or owner review, contact Support.

Bot Managers also receive alert DMs for CalicoTab access and announcement permission problems. See Bot Manager alerts.

Commands are missing

Participant commands

1. A server administrator opens Server Settings → Integrations → Moji Tournament Bot → Commands and allows /connect, /room, and /tab for the intended participant roles or @everyone.
2. In the participant channel, check Edit Channel → Permissions → Use Application Commands for those roles and any member overrides. See the command-access settings example.
3. Ask the participant to select /connect in that channel again.

Bot Manager commands

1. A server administrator with Manage Server or a configured Bot Manager runs /config status, including when the affected staff member cannot see it. Check that the staff member has a configured Bot Manager role.
2. If command access needs recovery, select Enable Bot Manager commands from /config status or /setup bot and complete Discord authorization. This repairs command visibility after a partial installation, role or command changes, or manual permission changes; it does not grant server permissions.
3. Run /config status again and confirm command access is Ready. Ask the staff member to try their command again.

Announcements or Command Log messages are missing

1. A Bot Manager runs /config status and follows the relevant Next action. Check the reported channel permissions and delivery health.
2. For Command Log permission failure on an existing server, reauthorize the bot with Manage Channels and run /setup bot once. If delivery is unknown, do not repeat message-sending commands; contact Support.
3. For draw or motion announcements, the Tab Team checks that the expected item is public in CalicoTab.
4. Once those checks pass, run /draw for a missing draw or /motion for a missing motion, once.

For a missing schedule or start-time announcement, follow the separate schedule or round-start instructions.

Motion veto needs recovery

1. A Bot Manager runs /config status to verify that motion veto is enabled. If disabled, a server administrator with Manage Server runs /config veto enabled:true.
2. The Tab Team confirms that the round has a published draw, released motions, and at least two motions in CalicoTab.
3. Run /veto start in the configured announcement channel. This starts or recovers the interactive motion veto session for the current public round immediately, without a preview.
4. In multi-room preliminary rounds, each debate room runs an independent veto in parallel. Debaters can submit preferences by clicking 🗳️ Submit Team Veto on the central announcement card, or 🗳️ Submit Motion Veto inside /room.
5. If motions were unreleased or edited in CalicoTab, the bot automatically cancels prior veto records and allows a fresh session upon rerelease.

A participant is not receiving DMs

A timeout does not prove a DM was not delivered. Draw and veto notifications with uncertain outcomes are not automatically resent after restart. Ask the participant to check DMs and use /room; do not repeatedly restart the bot or resend to everyone.

1. The participant checks their linking confirmation; a Bot Manager can check /link status and use the linking help if needed.
2. Ask the participant to allow direct messages from server members and check that they have not blocked Moji Tournament Bot.
3. For a draw or veto-result DM, the Tab Team checks that the draw or result is available. The participant runs /room to retrieve current details privately; this does not resend the missing DM.
4. For a manually sent /dm, the sender reviews the delivery result, then creates a fresh DM preview and confirms it. Select only the intended recipients to avoid sending another copy to everyone.

Recovery is confirmed when the participant can view their assignment or receives the retried message.

Roles or nicknames are not updating

1. A server administrator checks that Moji has Manage Roles for role changes and Manage Nicknames for nickname changes.
2. In Server Settings → Roles, move Moji above the role it needs to manage. For nicknames, it must be above the member’s highest role; it cannot change the server owner’s nickname.
3. A Bot Manager runs /update after participant or institution changes and checks the reply and affected member. Use /setup bot for missing standard roles or setup recovery, then check /config status.

If the wrong duplicate role is selected, follow role repair and duplicate cleanup.

A preview expired

1. The person who started the command reruns the command named in the expiry reply.
2. Review the new preview, then confirm or cancel using its controls. Only its creator can use them.

Private previews expire after five minutes; pending previews are also lost after a bot restart. Check the new confirmation reply to verify the action completed.

Change tournament credentials

Keeping the same tournament preserves participant links and scheduled work. Changing the tournament clears participant links, check-ins, timers, ballot reminders, vetoes, meeting link, and delivery history. Server settings, role mappings, and Bot Manager command access remain saved. Participants must link again for the new tournament.

1. A server administrator with Manage Server runs /setup bot.
2. Enter the tournament URL and API token in the private form. Keep tokens and Private URLs out of public chat and support messages.
3. Run /config status and resolve any Action needed items to verify the connection.

Successful setup restarts both cleanup timers.

Repair or merge duplicate roles

First choose the roles to keep. Deleting duplicates is a separate review and confirmation.

1. Choose and repair your roles

1. Run /role fix. For each group, select the Role to keep. Identical names use Candidate A/B labels.
2. Read the recommendation and its reason. It may suggest a different role from the configured one to preserve access; you must make the selection yourself.
3. Select Review changes, review all six groups, then confirm repairs. The chosen roles keep their members and permissions.

2. Review duplicate cleanup

1. Open Review duplicate cleanup. Safe matching duplicates are preselected; uncheck any you want to keep.
2. Select Review merge and deletion. Check the eligible, blocked and intentionally kept counts, then visit every review page.
3. Need to keep a different role? Use Change retained role to start a fresh selection without applying changes.

Before confirming: merging can change members’ access. Duplicate channel rules replace conflicting rules on the retained role; later duplicates in the displayed order win conflicts. Merging requires Manage Server and Manage Roles.

3. Confirm and check the result

1. Select Confirm merge and deletion. Mixed batches process eligible roles only; blocked roles stay untouched.
2. Watch the private progress reply. Moji Tournament Bot copies permissions and channel rules, transfers members, verifies the result, then deletes each duplicate. Progress includes counts and elapsed time.
3. Selected cleanup complete means all selected duplicates succeeded. Otherwise, follow the next action shown for each remaining role. Intentionally kept roles are not failures.

Blocked or incomplete?

• Command-access blocker: select Update Bot Manager command access, or run /config status if no link appears. Then select Refresh cleanup review and review again before confirming. This updates command access, not server permissions; the old confirmation cannot be reused.
• Permission blocker: fix the permission or role-order issue named in the reply, or change the retained role. Start a fresh review before retrying.
• Inspection failed: contact Support with the reported reason. Affected cleanup is disabled until inspection works; safe name repair remains available.
• Expired preview: previews expire after five minutes. Rerun /role fix for a fresh review.
• Partly completed: completed changes are preserved; a failed merge keeps its duplicate. Follow the reported next action, then rerun /role fix to retry remaining work.

After changing Bot Manager mappings, check /config status.

Temporary command pauses

If Bot Managers keep retrying while the bot asks them to wait, commands that refresh large amounts of data or post publicly may pause for ten minutes. The server owner and configured Bot Managers receive one DM, and /config status shows when the pause ends.

Participants can still use /room, /tab, /connect, and active check-in buttons. Setup and configuration commands also remain available. Wait until the time shown in the private reply before you try the paused command again.

Remove the bot

1. A server administrator with Manage Server runs /setup remove.
2. Review the private confirmation. Select Delete data and remove bot to proceed, or Cancel.
3. Check the result: the bot permanently deletes saved credentials, participant links, configuration, and scheduled work, then leaves the server.

Reinstalling starts a new setup. Removal also makes the bot leave when no saved configuration exists.

Report an error with a Support ID

1. Copy the 12-character Support ID from the error reply.
2. Send it to Support with the command name, server or tournament, and the approximate time and timezone.
3. If no Support ID is shown, send the error text or a sanitized screenshot instead.

The bot operator uses the code to find the matching sanitized log entry. Never include credentials, API tokens, or Private URLs.