Skip to main content
When a ticket action doesn’t go through, Lucie replies with the reason and, below it, a line like this one:
The link takes you straight to that code on the Spanish version of this page; here you have the same codes in English. The Ref. identifies that specific failure: if you write to the support server, include it and we’ll find it faster.
Many of these errors are configuration issues. /ticket debug checks Lucie’s permissions, the categories and every panel at once. The team and whoever manages the server can use it.

​
TK-DISABLED

Tickets aren’t enabled on this server.
Cause: the Tickets on switch is off, or the server hasn’t set up tickets yet. How to fix it: in the web panel, go to Support → Tickets, switch on Tickets on in the header and save. You need the Manage Server permission.

​
TK-PANEL

This panel no longer exists. Ask an admin to publish it again.
Cause: the button or dropdown option belongs to a panel that was deleted in the web panel or is no longer part of that message. It also shows up if the panel changed while someone was filling in its form, and with /ticket new if the server has no panels. How to fix it: post the message again (Update in the panel bar) so it only offers panels that exist. For /ticket new, create a panel or pick another one in Overview → Panel for /ticket new.

​
TK-BLACKLIST

You can’t open tickets on this server.
Cause: you have one of the server’s Roles without tickets. How to fix it: if it’s a mistake, ask whoever manages the server to remove that role from you or take it out of Overview → Roles without tickets. Whoever manages the server is never blocked.

​
TK-RATE

A rate limit. The message says which one: How to fix it: wait and try again. These are fixed limits and can’t be configured. Whoever manages the server and the Roles without limits don’t have the hourly or the server one.

​
TK-LIMIT

A ticket limit has been reached. The message says which one: In the limits you choose, 0 means no limit. Whoever manages the server and the Roles without limits skip the first four.

​
TK-FORM

Check what you wrote and try again.
Cause: something that was sent isn’t valid. The usual cases:
  • A required form question was left empty, or the form changed while you were filling it in.
  • !ticket new on a panel with a form: it can’t be shown through the prefix.
  • /ticket add or /ticket remove with no user or role, or with both at once.
  • !ticket add with something that isn’t a mention or an ID, or adding someone who isn’t in the server.
  • /ticket rename with no name.
How to fix it: fill in what’s missing and try again. To open a ticket with a form, use the panel’s button or /ticket new.

​
TK-PERMS

I’m missing permissions to do that: Manage Channels, Manage Roles.
Cause: Lucie is missing a permission to create, move or change the ticket’s channel, or to write in it. The message says which ones. If it says “the permissions of this channel or its category”, a permission override on the channel or the category is taking it away. How to fix it:
  • In the server, Lucie needs View Channel, Manage Channels, Manage Roles, Send Messages, Embed Links, Attach Files and Read Message History.
  • In each ticket category, View Channel, Manage Channels and Manage Roles: check its overrides.
  • /ticket debug tells you exactly what’s missing and where. The ticket guide has the full table under Permissions Lucie needs.

​
TK-NO-CATEGORY

The ticket category no longer exists. Let an admin know.
Cause: all of the panel’s Open tickets categories were deleted on Discord. How to fix it: in Opening → Categories, remove the deleted ones and add one that exists. If you leave the list empty, tickets are created without a category.

​
TK-CATEGORY-FULL

The ticket categories are full (50 channels). Let an admin know.
Cause: Discord allows 50 channels per category, and all of the panel’s Open tickets categories are full. How to fix it:
  • Add more categories (up to 5, in order): when one fills up, Lucie uses the next.
  • Set a Closed tickets category so closed tickets free up space in the open one.
  • Delete the closed tickets you no longer need.

​
TK-GUILD-FULL

This server has reached Discord’s channel limit.
Cause: Discord doesn’t allow more than 500 channels per server, categories included. How to fix it: delete channels or closed tickets. To keep it from happening again, leave some room with the Server limit in Overview.

​
TK-CONFIG

The ticket settings have a problem. Check the web panel.
Cause: something in the settings can’t be applied as it is. The most common case is a button with an emoji Lucie can’t use, because it’s from a server she isn’t in. On a ticket’s welcome message, Lucie retries with the default emojis. How to fix it: check the warnings in the Tickets section (the Buttons tab flags the emojis Lucie can’t use) and what /ticket debug says. Fix it, save and press Update to post the panel again.

​
TK-NOT-TICKET

This command only works inside a ticket.
Cause: you used a ticket command (close, claim, add…) outside a ticket’s channel, or in one that’s no longer active. How to fix it: use it inside the ticket’s channel. Only /ticket new and /ticket debug work in any channel.

​
TK-DENIED

You can’t do that in this ticket.
Cause: that action isn’t yours to take. For example:
  • Reopening, deleting, claiming, adding, removing, renaming, saving the transcript, requesting closure, the User card and /ticket debug are for the panel’s team.
  • The person who opened the ticket tries to close it and the panel has The author can close it turned off.
  • Claiming with Allow claiming off, or pressing User card with User card turned off in the settings.
  • Answering a close request that isn’t yours: only the author answers.
  • Adding or removing @everyone, Lucie or the author, removing whoever is handling the ticket, or touching a team or additional role.
How to fix it: ask someone on the team to do it. To be part of the team, your role has to be in Team roles (Team tab); team and additional roles are changed there, not with add and remove.

​
TK-STATE

The ticket is no longer in a state that allows that.
Cause: the ticket changed before your action arrived, or it isn’t in the right state: closing one that’s already closed, reopening an open one, claiming or requesting closure on a closed one, releasing one nobody is handling or answering a close request that no longer exists. It also shows up if the ticket’s channel no longer exists. How to fix it: check where the ticket stands (the channel’s latest messages) and repeat the right action. Usually there’s nothing to fix.

​
TK-CLAIMED

@usuario is already handling this ticket.
Cause: you’re trying to claim a ticket another team member already has, or to release someone else’s with Only the claimer releases it turned on. How to fix it: ask that person to release it. If the team should be able to take tickets from each other, turn on Take over a claim in Team → Claiming. Whoever manages the server always can.

​
TK-BUSY

Another action is in progress on this ticket. Try again in a few seconds.
Cause: someone is doing something else with the same ticket at the same time (for example, closing it while another person adds a user), or you pressed Open ticket twice and the first one is still being created. How to fix it: wait a few seconds and try again. If you get it when opening, your ticket is most likely already being created.

​
TK-EXPIRED

This button has expired.
Cause: the button comes from an old message: from a previous version of tickets, from a ticket that no longer exists or from a ticket on another server. How to fix it: if it’s the panel’s button, press Update in the panel bar to post it again. Inside a ticket, use the /ticket commands.

​
TK-TRANSCRIPT

A transcript couldn’t be saved. The message says why: How to fix it: check that Lucie has View Channel and Read Message History in the ticket and try again in a minute. If it’s the daily limit, wait until the next day.
When closing or deleting, a failed transcript doesn’t stop the action: the ticket is closed or deleted anyway and the log comes out without a link.

​
TK-UNKNOWN

Something went wrong.
Cause: an unexpected failure on Lucie’s or Discord’s side. How to fix it: try again in a few seconds. If it keeps happening, write to us on the support server with the message’s Ref. and what you were doing.