Troubleshooting

It does not answer#

Work down this list. Some of these a member can fix, and the permission and block causes need an admin.

• It was not addressed. Xertron only answers when you mention it, reply to one of its messages, or write in a thread it started. See When it answers.
• It is a direct message. Xertron has no DMs and never sees one. Use a server.
• The sender is another bot or a webhook. It ignores them by default, and an admin can only let it read specific apps. A person still has to make it respond.
• It cannot see or write in that channel. A permission was taken away there. The dashboard’s Permission health screen names the channel and the missing permission. See Add it to your server for the six it needs.
• You were blocked. An admin can stop one member using Xertron in the server. Ask them, since only an admin can lift it. See Blocking one member.
• You sent messages too fast. It asks you to slow down instead of answering. Wait a moment and send it again.

The status message never turns into an answer#

Xertron posts a short status message, then edits the finished answer into it. If the status line stays and nothing replaces it, check whether the channel has slowmode on. Without Bypass Slowmode, Xertron never gets to post the answer there.

An admin fixes this in the channel’s permissions: allow Bypass Slowmode for Xertron’s role. The dashboard’s Permission health screen names any channel where a permission is missing.

Replies are lighter than usual#

Xertron steps down in capability as a server uses up its monthly limit instead of stopping. The Pro model gives way to flash, deeper thinking gives way to standard, and it says so when a reply came out lighter for that reason. The usual causes:

• The server, or your role’s share, is nearly used up. Run /usage to see how much is left and when it resets. See Running out.
• Eco mode is on. An admin can hold everyone to the fast model with no extended thinking. Quick, simple replies are then the setting working.
• Your role was not given the feature. Admins grant the Pro model and deeper thinking per role. See Opening premium features.
• The server is on the free plan. The Pro model and deeper thinking need Premium, and they go with the plan if a server goes back to free. See If a server goes back to free.

It says it cannot do something#

A premium feature can be held back at up to three levels, and a different person fixes each. Image generation passes through all three and its message names the one that applies; the others pass through only some:

• The plan. The server needs Premium for the Pro model, reading images, generating images, web search, memory, connectors and custom personas. See What each one covers.
• A server toggle. Web search and image generation are off by default even on Premium. An admin turns them on from the dashboard’s Overview screen. See On Premium but off by default.
• Your role. Admins grant the Pro model, deeper thinking and image generation per role. If none of your roles has the grant, the answer says that specifically.

Image generation has a fourth case that is not a gate: the generator filters the picture it made, so a borderline prompt can pass one attempt and be refused the next. A refusal is free, so rephrase or run it again. See When it will not.

A file was ignored or cut short#

• No reply to a file. A text file, PDF or Word document sent with no message text is stored quietly: no reply and no reaction. Ask about it in your next message and it already knows what is in it.
• It only read the start. The free plan reads 10,000 characters of a file and Premium reads 500,000. Past about 5,000 characters it searches the file by meaning instead of reading it front to back.
• It could not see an image. Reading images needs Premium. On a free server it reacts to say so.
• It said storing failed. Send the file again.

See Files and images.

The clear flag did nothing#

!clear only works with a mention or as a reply to one of its messages, so write @Xertron !clear. A bare !clear is ignored on purpose. Inside a thread there is nothing to clear, because a thread remembers everything back to its start. Leave it and start another. See Starting over.

Still stuck#

Ask Xertron in your own server. It knows its feature set, what your plan includes and why it turned something down, and its answer is about your server rather than the general case.