Troubleshooting

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.

TC000 - Internal ErrorCopy Anchor Link

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, feedback, or on-call update failed; ModMail could not open a ticket. 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.

TC001 - Rate LimitedCopy Anchor Link

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 (each change renames the channel)
• Renaming, closing, or reopening the same ticket repeatedly within 10 minutes
• Pinning a ticket: the pin is saved but Discord could not move the channel to the top yet
• Sending ModMail messages too quickly; the message says how many seconds to wait

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

TC002 - Permission DeniedCopy Anchor Link

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, /on-call toggle, 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
• 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
• Being blocked by the firewall, or by ModMail account age or membership age rules
• Using another staff member's /claims controls

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
• /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 thread ticket without Manage Threads
• 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.

TC004 - Resource Not FoundCopy Anchor Link

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: the ticket category was deleted from Discord
• 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
• /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

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.

TC005 - Discord API ErrorCopy Anchor Link

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 ResourcesCopy Anchor Link

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 SelectionCopy Anchor Link

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 ActionCopy Anchor Link

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
• 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 FoundCopy Anchor Link

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: no transcript 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 Closing tickets → Transcripts, map every dropdown option to a category under Panels → Ticket panels, and save. See Configuration.

TC012 - Input Validation ErrorCopy Anchor Link

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
• /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; /on-call or /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

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

TC013 - Ticket CooldownCopy Anchor Link

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.

TC014 - Plan RequiredCopy Anchor Link

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
• /approval below Enterprise
• The trial's 1,000,000 AI token allowance has been used up

Fix: the bot owner can upgrade under Plan & billing in the dashboard (plans are compared at ticketcord.com/pricing). Everything that does not need the higher plan keeps working.

TC015 - Ticket State ConflictCopy Anchor Link

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
• 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, claiming your own ticket, 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
• Escalating a ticket that was already escalated to staff
• Undoing a knowledge base change that was already reverted or updated since

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

TC016 - Ticket Limit ReachedCopy Anchor Link

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; configurable from Basic under Opening tickets → Ticket options → Open at the same time)
• 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)

Fix: close an existing ticket, or ask an administrator to raise the limit in the dashboard.

TC017 - Wrong ContextCopy Anchor Link

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
• Reopening a ModMail ticket with /reopen
• 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 UnavailableCopy Anchor Link

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
• Translation is not enabled for the server, or is already disabled on the ticket
• 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
• ModMail is not enabled on the selected server

Fix: enable the feature in the dashboard or wait for business hours. For ModMail servers, send the bot a direct message instead of pressing a button.

TC019 - Discord Limit ReachedCopy Anchor Link

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
• Every configured ticket category already holds 50 channels

Fix: delete unused channels (turn on Delete the channel on close under Closing tickets → Closing rules so closed tickets clean themselves up), add another ticket category under Opening tickets → Ticket categories (when one is full, the next one is used), or switch to thread tickets.

Common issuesCopy Anchor Link

Bot is offlineCopy Anchor Link

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.
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.

Tickets are not being createdCopy Anchor Link

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.

Staff cannot see ticketsCopy Anchor Link

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.

Transcripts are not generatedCopy Anchor Link

Causes: no transcript channel configured (TC011); the bot lacks Send Messages or Attach Files there; automatic transcripts on close are off.

Fix: set Post transcripts in under Closing tickets → Transcripts, and give the bot Send Messages, Embed Links, and Attach Files in that channel. A transcript is posted automatically on close only when Post a transcript when a ticket closes is on under Closing tickets → Closing rules. Otherwise, press Transcript on the closed ticket or run /transcript.

Slash commands do not appearCopy Anchor Link

Causes: 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 commands are still missing for everyone, kick the bot and invite it again with Invite to a server in the dashboard.

Common questionsCopy Anchor Link

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. 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 and the bot's server-level permissions, and lists errors and warnings.

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