Troubleshooting

Every TC error code with the situations that produce it and the fix, plus the most common bot problems

When something goes wrong, the bot replies with a short message and a TC code. Find the code below: each section lists the concrete situations that produce it and what to do. If your problem has no code, jump to Common issues.

How to spot a TicketCord error. Every error the bot sends starts with a ❌ marker and ends with a footer line showing the code, the TicketCord name (or your custom branding), and a Learn more link:

❌ Only staff members can claim tickets.
-# TC002 • TicketCord • Learn more

Error cards (the red panels used for close, delete, reopen, setup, and purge failures) show the same code at the start of their footer. Ticket and command errors always carry a code (the only exceptions are the short private replies from /feedback).

An error about a panel button or a ticket command that has no TC code is not from TicketCord, even if it comes from a bot with the same name. That usually means another bot or script is running on the same token; see Bot is offline.

Codes TC003, TC006, and TC007 are not in use. If you see one, the message did not come from TicketCord.

TC000 - Internal Error

What it means: something failed on TicketCord's side rather than because of your input or configuration.

Situations that produce it: a ticket could not be created, closed, claimed, renamed, reopened, or deleted because of a storage error; a note, tag, transcript, summary, or statistics request could not be saved or loaded; /setup failed part-way and lists leftover resources; an approval or feedback update failed; ModMail could not open a ticket; an email reply could not be sent (see Email Inbox). The message usually says which action failed.

Fix: try again in a moment. If it keeps happening, check the logs channel for details and contact support with the time and the command you used. TC000 errors are reported to the team automatically.

Email replies: do not simply try again in these two cases, or the customer may get the same email twice:

  • The email was sent, but it could not be added to the ticket's history. Do not send it again. The customer got the email. Do not press Send or write it again; only the ticket's record of it is missing.
  • It could not be confirmed whether the email was sent. The draft is kept, but the customer may already have it. Check with the customer, or wait for their reply, before you press Send again.

Other email actions (see Email Inbox):

  • The sender could not be blocked. Try again in a minute. Nothing was blocked. Press Block sender again after a minute; blocking the same sender twice is harmless.
  • The visitor could not be blocked. Try again in a minute. Nothing was blocked. Press Block visitor on the website widget ticket's opening card again after a minute.
  • The tickets could not be merged. Press Merge again to finish. The merge stopped part way. Pick the same ticket in Merge into another ticket and press Merge again: it finishes the remaining steps without posting anything twice.

TC001 - Rate Limited

What it means: Discord is temporarily refusing requests because too many were sent too quickly.

Situations that produce it:

  • Changing priority more than twice in 10 minutes, with /priority or on the dashboard (each change renames the channel)
  • Renaming or reopening the same ticket repeatedly within 10 minutes
  • Running /setup while Discord is limiting the bot's requests
  • Pinning a ticket: the pin is saved but Discord could not move the channel to the top yet
  • Sending more than 5 ModMail messages to the bot in one minute; the message says how many seconds to wait
  • Sending the Use examples form more than 5 times, or asking for a new Preview more than 10 times, in an hour on your /ai-style card

Fix: wait 10 to 15 minutes and try again. This is a Discord limit, not a TicketCord one.

The /ai-style limits are TicketCord's own, counted per staff member and server: try again later in the hour. A preview already shown in the last hour for the same choices does not count.

The ModMail limit is the other exception: it is TicketCord's own, counted per member and per bot, and it also applies to a member who already has an open ticket. A message over the limit is not relayed or queued, so staff never see it. It gets a ❌, the first one also gets this error, and the member needs to send it again once the wait is over.

A pin is still saved when you hit this limit, and the channel name updates on its own once the limit resets. The same goes for a claim mark and an automatic priority emoji. A close still goes through and the channel keeps its current name. A priority you set yourself is not saved, so set it again after the wait.


TC002 - Permission Denied

What it means: you, or the bot, lack a permission the action needs.

Situations where you lack the permission:

  • Using a staff command (/claim, /note, /priority, /stats, /summary, /transcript overrides, /closerequest, Find ticket, and others) without a role selected under Staff → Staff roles in the dashboard
  • Closing, renaming, adding, removing, or pressing Extend Time on a ticket you did not create and are not staff for
  • Closing your own ticket when Only staff can close is on
  • Answering a close request that was sent to someone else
  • Pressing Confirm or Cancel on a /close confirmation someone else started
  • /closerequest in a ModMail ticket when the member's DMs are closed, so the request cannot reach them
  • Unclaiming a ticket you did not claim (and you are not staff)
  • Removing a supervisor from a ticket
  • Adding someone other than staff, or a role other than a staff role, to a ModMail ticket
  • Removing someone else's note
  • Approving or rejecting without the approval role
  • Running /setup without Administrator or Manage Channels and Manage Roles, /config without Administrator or a staff role, or /purge (or its confirmation) as anyone but the server owner
  • Changing staff roles in /config as anyone but the bot owner or the Discord server owner ("Only the bot owner or the server owner can change staff roles.")
  • Being blocked by the firewall, or by ModMail account age or membership age rules
  • Pressing a panel button, or picking a dropdown option, whose Who can open this rule blocks one of your roles or allows only roles you do not have
  • Using another staff member's /claims controls
  • Using the controls on someone else's /ai-style card
  • Opening a thread ticket when you cannot see the channel thread tickets open in: with public threads, a server administrator needs to give members View Channel and Send Messages in Threads there; with private threads, the bot gives you access itself, so it needs Manage Permissions in that channel

Situations where the bot lacks the permission:

  • Creating a ticket channel: the bot needs Manage Channels and Manage Permissions on its role, and View Channel, Manage Channels, Manage Permissions, Send Messages, and Embed Links in the ticket category
  • Bot Cannot Access This Server: the bot's role lost View Channel at the server level
  • /embed: the bot lacks View Channel, Send Messages, or Embed Links in the target channel
  • /setup: the bot lacks Manage Channels and Manage Roles at the server level, or cannot reach a channel or role it needs (Missing Access: its role is below the roles it manages)
  • /add or /remove: the bot lacks Manage Channels and Manage Permissions (plus Manage Threads for thread tickets) to change who can see the ticket
  • Renaming a ticket (/rename or the dashboard) without Manage Channels, or a thread ticket without Manage Threads
  • Deleting a thread ticket without Manage Threads in its thread channel: the thread is archived instead and the ticket stays closed
  • Server 2FA Requirement: the server requires two-factor authentication for moderation and the Discord account that owns the bot application does not have it enabled

Fix: for your own permissions, ask the bot owner to add your role under Staff → Staff roles. For the bot, open Server Settings → Roles, drag the bot's role above the staff roles, and confirm it has the permissions listed on Installation; then check the category's own permission overwrites for the bot, and run /diagnose. For 2FA, enable it on the Discord account that owns the application.

Go to Staff → Staff roles

Inviting the bot any other way than from the dashboard (your own invite link, or Discord's Add App button on the bot's profile) is not supported, and its permissions are probably incomplete. Kick the bot and invite it again with Invite to a server in the dashboard.


TC004 - Resource Not Found

What it means: a channel, category, role, ticket, user, embed, or canned response that TicketCord needs no longer exists or could not be found.

Situations that produce it:

  • Category Not Found: every ticket category selected for the panel or server was deleted from Discord (while one of them still exists, new tickets skip the deleted ones and open there)
  • A warning in the logs channel that every staff role was deleted: all staff roles of the server, or all staff roles picked for a panel button or form, no longer exist, so staff cannot see its new tickets (see Deleted roles and categories)
  • TicketCord isn't a member of this server: the bot was kicked
  • /add or /remove: the user, role, or ticket ID does not exist, or the target does not have access to the ticket
  • /add role on a thread ticket: nobody has the role
  • /embed: no saved embed with that name, or the target channel was deleted or is inaccessible
  • /reply: no canned response with that shortcut
  • /tag remove: the tag is not on the ticket
  • Renaming a ticket whose Discord channel was deleted
  • /summary: the ticket has no messages to summarise
  • /modmail message: the number is beyond the transcript length
  • /config or setup wizard: the server has no categories or no text channels
  • ModMail: no server with ModMail enabled that you are a member of
  • A ticket button pressed after the ticket was deleted (Ticket not found.)
  • Block visitor on a website widget ticket whose widget this server no longer has (it was moved or removed), so the visitor cannot be blocked from that ticket

Fix: open your server, replace the missing category, channel, or role on the settings page that uses it (for example Opening tickets → Ticket categories), and save. If you need fresh ones, create them in Discord or run /setup again, then pick them on that page. For a kicked bot, invite it again with Invite to a server in the dashboard.

Go to your server Go to Opening tickets → Ticket categories

TC005 - Discord API Error

What it means: Discord returned an error while the bot was updating a channel.

Situations that produce it: reopening a ticket when Discord refuses the rename or move.

Fix: wait a minute and try again. If it persists, check Discord Status.


TC008 - Failed to Fetch Resources

What it means: the bot could not load something from Discord or verify your permissions in time.

Situations that produce it:

  • The bot could not read the server's roles, channels, or categories (setup wizard, /config)
  • Staff or owner verification timed out for a command (/claim, /close, /note, /priority, /summary, /transcript, /unclaim, /purge, and others)
  • The bot could not identify your Discord account, or could not check the bot owner's plan
  • Couldn't check the bot's permissions during /setup

Fix: try again in a few seconds. If it keeps happening, confirm the bot has View Channel at the server level and that Discord is not having an outage.


TC009 - Invalid Selection

What it means: nothing was selected, or the selection is not one of the allowed choices.

Situations that produce it:

  • A dropdown, role picker, channel picker, or reason picker was submitted with nothing chosen
  • An application form answer is not one of the allowed choices
  • No server was selected in the ModMail server picker

Fix: pick an option and submit again.


TC010 - Unknown Action

What it means: the bot received a button, menu, subcommand, or wizard step it does not recognise.

Situations that produce it:

  • Pressing buttons on a panel posted by an older configuration whose buttons were removed or regenerated
  • Pressing a button that belongs to a different bot or application
  • Using /claims controls from an old card
  • Using /ai-style controls from an old card
  • A subcommand the bot does not know (for example after a partial command update)

Fix: ask an administrator to post the panel again from Panels → Ticket panels, or run the command again to get a fresh card. If a message with a TC footer still fails, contact support.


TC011 - Configuration Not Found

What it means: the server, or the feature you used, has not been configured yet.

Situations that produce it:

  • This server hasn't been set up yet: the essentials were never saved in the dashboard
  • The ticket category is not configured
  • A dropdown option is not mapped to a ticket category
  • A ticket button or form refers to configuration that no longer exists
  • /transcript: neither a transcripts channel nor a logs channel is configured
  • /embed: no embeds have been created yet
  • /approval: the approval process is not configured
  • The setup wizard session expired

Fix: open your server. If the server was never set up, its home page shows the setup form: fill it in and click Finish setup. Otherwise check Staff → Staff roles, Opening tickets → Ticket categories, and General → Where the bot posts, map every dropdown option to a category under Panels → Ticket panels, and save. See Configuration.

Go to your server Go to Staff → Staff roles Go to Opening tickets → Ticket categories Go to Closing tickets → Transcripts

TC012 - Input Validation Error

What it means: a value you gave is missing, too long, or in the wrong format.

Situations that produce it:

  • /auto-close: not a format like 30M, 2H, or 1D; under 15 minutes; or over 30 days
  • /close in:: not a delay like 30m, 2h, or 1d
  • /rename: empty, over 80 characters, or nothing valid left after removing unsupported characters
  • /note add: over 1000 characters; /note remove: number out of range
  • /tag: empty, over 50 characters, or characters other than letters, numbers, hyphens, and underscores
  • /add or /remove: both or neither of user and role, a bot user, or the @everyone role; removing the ticket's creator from the dashboard (in Discord, /remove asks for confirmation instead)
  • /approval reject without a reason
  • /config: more than 10 staff roles selected
  • /embed: the embed contains an emoji the bot cannot use (deleted, or from a server the bot is not in)
  • Find ticket with no member selected; /tag with no subcommand
  • A button or form that is no longer valid (This form is no longer valid. Please open it again)
  • An application upload that could not be read
  • A purge confirmation that is out of date
  • An email reply that is empty or longer than 3,000 characters, or a draft too long to translate (see Email Inbox)

Fix: correct the value and try again. For expired buttons and forms, start again from a fresh message.


TC013 - Ticket Cooldown

What it means: a ticket for you is already being created, or you are creating tickets too quickly.

Situations that produce it:

  • Pressing Open Ticket or submitting a form twice within a few seconds
  • Opening tickets one after another in quick succession
  • Extending an auto-close reminder repeatedly
  • Running /setup while TicketCord is already creating the server's categories and roles, from the dashboard or another /setup
  • Sending a new ModMail message right after a ModMail ticket closed; the message says how many minutes to wait

Fix: wait about ten seconds and try again. The limit is per member, per server.

If you pressed the button twice, only the first ticket is created. The duplicate press is ignored.


TC014 - Plan Required

What it means: the feature needs a higher TicketCord plan than the bot owner has.

Situations that produce it:

  • Application forms, /auto-close, /stats, or /reply on the Free plan
  • A canned response beyond the first 25 on Basic or Pro
  • /ai-help, /summary, or AI priority detection below Pro
  • /ai-style below Pro with no saved style, or Use examples or Preview on its card below Pro
  • /approval below Enterprise
  • The trial's 1,000,000 AI token allowance has been used up
  • /ai-help, or Use examples or Preview on the /ai-style card, when the bot owner's AI tokens for the month are used up

Fix: the bot owner can upgrade under Plan & billing in the dashboard (plans are compared at ticketcord.com/pricing). When AI tokens are used up, AI features pause until the next monthly reset, or the owner can add tokens on the AI usage page. Everything that does not need the higher plan keeps working.

Go to Plan & billing

TC015 - Ticket State Conflict

What it means: the action does not fit the ticket's current state.

Situations that produce it:

  • Closing, claiming, unclaiming, renaming, adding, removing, or extending a ticket that is already closed
  • Drafting or sending an AI Help reply on a closed ticket
  • Reopening a ticket that is already open, or one that is being deleted
  • Deleting a ticket that another delete is already removing
  • Claiming a ticket that is already claimed, or unclaiming a ticket nobody claimed
  • Adding a user or role that already has access
  • Removing the staff member who holds a ticket's exclusive claim
  • Adding a tag that already exists, or clearing tags when there are none
  • Requesting an approval when one is already pending, approved, or rejected; deciding when nothing is pending; or deciding after another approver already did
  • Extending a ticket again before the next reminder
  • Deleting a ticket that is not closed
  • Pressing Confirm or Cancel on a /close confirmation that expired or was already used: run /close again if the ticket is still open
  • Pinning a ticket that is already pinned, or unpinning one that is not
  • Pinning a closed ticket whose channel is being deleted
  • Escalating a ticket that was already escalated to staff
  • An email draft that was already sent, discarded or expired (drafts last 24 hours), is being sent by someone else, or changed since its card was shown (see Email Inbox)
  • Merging email tickets that cannot be merged (These tickets cannot be merged. Both must be open email tickets from the same sender in this server.): one of them is closed or already merged, or they are from different senders. Check both tickets; a ticket that was already merged needs nothing more (see Merge tickets)
  • Undoing a knowledge base change that was already reverted or updated since
  • Answering a close request that is more than 7 days old, or one sent before the ticket was reopened

Fix: check the ticket's status and use the matching action. Reopen a closed ticket before changing it.


TC016 - Ticket Limit Reached

What it means: a per-member or per-ticket limit has been hit.

Situations that produce it:

  • The member already has the maximum number of open tickets (5 on Free unless you lowered it; any limit from Basic under Opening tickets → Ticket options → Open at the same time). ModMail tickets do not use this limit: a member can have one ModMail ticket open at a time
  • The member has opened as many tickets as the server allows in total (from Basic, under Opening tickets → Ticket options → Total, including closed). Closed tickets count toward this limit, so closing one does not help; it applies to ModMail tickets too
  • All auto-close extensions for the ticket have been used
  • The ticket already has the maximum number of tags (10 by default, up to 25, set under Staff → Tags)
  • Sending an email reply when the server's daily or monthly email limit is reached (The email limit for this server is reached, so the email was not sent.). The draft stays and can be sent once the limit resets, as long as it is still there: drafts expire 24 hours after they were written. After that, press Reply on the customer's email and write it again. See Email Inbox limits
  • Blocking an email sender when the server already blocks 500 senders (This server has blocked the most senders it can (500).). The bot owner unblocks some on the Blocked senders card of the Email inbox page, then staff press Block sender again (see Block a sender)
  • Blocking a website widget visitor when the server already blocks 500 visitors (This server has blocked the most visitors it can (500).). The bot owner unblocks some under Blocked visitors on the Website widget page (see Block a visitor)

Fix: close an existing ticket (for the open-ticket limit), or ask an administrator to raise the limit in the dashboard. For the open-ticket limit, the message links the member's open tickets (up to 5), so they can go straight to one and close it. A thread ticket that Discord archived after a period of inactivity is still open and still counts: it drops out of the channel list, so use the link to open it, then close it with the Close button or /close. A panel ticket whose channel or thread was deleted in Discord stops counting on its own: it is recorded as deleted and kept in your history.

Go to Opening tickets → Ticket options Go to Staff → Tags

TC017 - Wrong Context

What it means: the command was used somewhere it does not apply.

Situations that produce it:

  • Running a ticket command (/close, /claim, /note, /priority, /transcript, and others) outside a ticket channel
  • Running /add or /remove outside a ticket without the ticket option
  • Running any command in a DM
  • Posting /embed inside a ticket channel
  • Using /close in: outside a ModMail ticket, or /modmail in a non-ModMail ticket
  • Using an application action on a ticket that is not an application

Fix: run the command inside the ticket channel or server it belongs to.


TC018 - Feature Unavailable

What it means: the feature is turned off, not supported here, or not available right now.

Situations that produce it:

  • Ticket creation outside the configured business hours
  • The server uses ModMail mode, so panel buttons are disabled; DM the bot instead
  • A panel button or form that was deactivated or whose embed was deleted
  • The approval process, or that approval type, is not enabled for the server
  • Adding a role with more than 100 members to a thread ticket
  • A /config setting that is managed from the dashboard only
  • Combining /close in: with silent
  • The bot is in maintenance mode, or ticket creation is paused for this bot
  • Knowledge base voting or feedback is temporarily unavailable
  • A vote button under an earlier AI answer after Let members rate answers, the knowledge base or Atlas was turned off (Voting is turned off for these answers.)
  • AI Help, /ai-help, /summary, /translation, or Use examples and Preview on the /ai-style card while the Atlas switch is off. AI Help, /ai-help, Use examples and Preview also need the AI Help drafts card on, and /translation needs Translate tickets on (Translation is not enabled for this server.)
  • An AI action in a ticket Atlas is kept away from: the member who opened it is on Keep Atlas away from, or it was opened from a panel button that turns Atlas off (Atlas is turned off for this ticket.)
  • ModMail is not enabled on the selected server, or the member left that server after the server list appeared
  • ModMail: no server you are in has ModMail on, and no ModMail server takes DMs from a server you are in
  • /remove targeting the member who opened a ModMail ticket: they write from their DMs and have no access to remove. Close the ticket, or block them in Opening tickets → Who can open tickets
  • Reopening a ModMail ticket with /reopen: ModMail tickets cannot be reopened, and the member's next DM to the bot opens a new ticket
  • Email tickets: sending is paused for the server, email is not available for the ticket, the customer's address bounced or reported spam before, or the draft could not be translated. See Email Inbox

Fix: enable the feature in the dashboard or wait for business hours. For an AI action, turn on the Atlas switch and the feature's card on AI assistant → Atlas, remove the member from AI assistant → Atlas → Keep Atlas away from, or wait for (or reset) their AI assistant → Atlas → Limit per member. For ModMail servers, send the bot a direct message instead of pressing a button. For ModMail in a private server that members are not in, select their server under Also take DMs from in ModMail → ModMail (see ModMail From Other Servers).

Go to General → Business hours Go to ModMail → ModMail Go to AI assistant → Atlas

TC019 - Discord Limit Reached

What it means: Discord's own capacity limits block the action.

Situations that produce it:

  • The server has reached Discord's limit of 500 channels, when a ticket opens or /setup runs
  • Every category of the button or option is full, the bot could not copy the last one (it lacks Manage Channels or a permission the category's overwrites set, or the server has 500 channels), and every spare ticket category (one no button or option uses) already holds 50 channels. A full button never borrows another button's category.

Fix: delete unused channels (set After closing to Delete the channel under Closing tickets → Closing rules so closed tickets clean themselves up), give the bot Manage Channels and the permissions its ticket categories' overwrites set so it can copy a full category (overwrites that set Manage Roles need Administrator), add another ticket category under Opening tickets → Ticket categories and either add it to the button with Add a category for when it's full in the panel designer or leave it unused by every button as a spare, or switch to thread tickets.

Go to Closing tickets → Closing rules Go to Opening tickets → Ticket categories

TC020 - Linked Account Required

What it means: the server requires a linked game account to open a ticket, and the member has not linked it.

Situations that produce it:

  • The server requires a Steam account and the member has not linked one in this server
  • The server requires a Roblox account and the member has not verified one with Bloxlink in this server

Fix (members): for Steam, press Link Steam on the reply, sign in through Steam on the page that opens, then open the ticket again. For Roblox, press Verify with Bloxlink on the reply and verify on the page that opens, or run Bloxlink's /verify command in the server, then open the ticket again. If Bloxlink is unavailable, TicketCord lets the ticket through rather than blocking it.

Fix (server owners): turn off the requirement in the game accounts settings if members should be able to open tickets without a linked account.


Common issues

Bot is offline

Causes: the token was reset in the Developer Portal; a privileged intent was turned off (Discord error 4014); the bot was kicked; or the same token is running somewhere else, so another process answers instead of TicketCord.

Fix:

  1. Check the bot is still in the server.
  2. If the token was reset, open the bot's Bot profile page in the dashboard and click Update token.
  3. Enable Server Members Intent and Message Content Intent on the Bot tab in the Developer Portal, then press Restart on the bot's Bot profile page. When the intents are the problem, the bot's notice in the dashboard says so and has an Open Developer Portal button. For a bot whose servers have more than 10,000 members together, Discord has to approve the intents before they can be turned on, so TicketCord cannot do it: apply for them in the Developer Portal, then turn both on once approved. For help with Discord's form, open a ticket in our support Discord: we send you answers you can mostly copy and paste, and mark the few details only you can fill in.
  4. If replies arrive without a TC code footer, stop the other bot or script using the token, reset the token, and update it on the bot's Bot profile page.
Go to Bot profile

Tickets are not being created

Causes: no panel has been posted; the configuration was never saved (TC011); the bot lacks permissions in the ticket category (TC002); the category is full (TC019).

Fix: run /diagnose, fix anything it reports, confirm the essentials are saved in the dashboard, and post the panel from Panels → Ticket panels or with /embed.

Go to Panels → Ticket panels

Staff cannot see tickets

Causes: their role is not selected under Staff → Staff roles; the role exists in Discord but was never saved in the dashboard; the category's permission overwrites hide it.

Fix: the bot owner selects the role under Staff → Staff roles and saves. Then check the ticket category allows the role to view channels.

Go to Staff → Staff roles

Transcripts are not generated

Causes: neither a transcripts channel nor a logs channel is configured (TC011); the bot lacks Send Messages or Attach Files in the channel; automatic transcripts on close are off.

Fix: set Staff logs, and Transcripts if transcripts should go to their own channel, under General → Where the bot posts. Left at Same as logs, transcripts go to the logs channel. Give the bot Send Messages, Embed Links, and Attach Files in that channel. A transcript is posted automatically on close only while the Closing tickets → Transcripts card is on. Otherwise, press Transcript on the closed ticket or run /transcript.

When an automatic transcript fails, a ticket set to be deleted on close is kept instead, so the conversation is not lost.

Go to General → Where the bot posts Go to Closing tickets → Transcripts

Slash commands do not appear

Causes: another program or bot host runs with the same bot token and replaced TicketCord's commands (Discord then shows commands that are not TicketCord's, such as /blacklist); the invite lacked the applications.commands scope; Discord's command cache is stale; you lack the default permission for that command.

Fix: reload Discord with Ctrl+R (Cmd+R on Mac). If other commands show instead of TicketCord's, stop the other program (or reset the token and update it in TicketCord), then use Fix commands. If commands are still missing for everyone, kick the bot and invite it again with Invite to a server in the dashboard.

Common questions

Where do I find the error code? At the end of the error message, in the small footer line, for example TC002. Error cards show it at the start of their footer.

The error has no code. Is it from TicketCord? Almost certainly not. Ticket and command errors from TicketCord carry a TC code (only /feedback's short private replies do not). A panel or ticket error without one comes from another bot or script, most likely one using the same token.

Is TC001 something I can fix? Not directly; it is Discord's rename limit of two per channel per 10 minutes. Avoid rapid priority changes and renames, and wait 10 to 15 minutes when it happens.

Why do I get TC002 when I have Administrator? Staff commands check the roles selected under Staff → Staff roles in the dashboard, not Discord permissions. Administrator only bypasses the check for /close and /config, and even in /config only the bot owner or the Discord server owner can change staff roles. Ask the bot owner to add your role there.

How do I know whether the bot's permissions are right? Run /diagnose in the server. It checks every configured channel and category (with thread tickets, also the thread channel and the bot's thread permissions there) and the bot's server-level permissions, and lists errors and warnings.

A member cannot open a ticket but others can. They probably have the most open tickets your limit allows already (TC016), are blocked by the firewall (TC002), or pressed the button twice (TC013). Ask them for the code in the footer.

Last updated on

On this page