> For the complete documentation index, see [llms.txt](https://docs.asagi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.asagi.xyz/help-and-reference/troubleshooting.md).

# Troubleshooting

Use this page when an Asagi feature is configured but does not behave as expected.

Feature-specific guides contain additional checks for their own settings.

### Start Here

Before changing the configuration, check these five things:

1. **Asagi is still installed on the server.**
2. **The configured channel, role, or message still exists.**
3. **Your latest dashboard changes were saved.**
4. **Asagi has the Discord permissions required for the action.**
5. **Asagi's role is high enough in the role hierarchy.**

If the feature requires Premium, also confirm that the server still has an active **Premium bonus**.

### The Server Does Not Appear in the Dashboard

Make sure:

* you are signed in with the correct Discord account;
* Asagi is installed on the server;
* you are the server owner, have **Administrator**, or have an Additional Bot Master role.

If Asagi was just added or your access was just changed, refresh the server list.

### A Dashboard Page Says I Have No Access

Dashboard access can change when your Discord roles or permissions change.

If you previously had access, check whether:

* an Administrator permission was removed;
* your Additional Bot Master role was removed from you;
* the role was removed from the Bot Masters settings;
* you are using a different Discord account.

A user who only has Bot Master access cannot edit the Bot Master role list itself.

### Changes Do Not Save

First check the message shown by the dashboard.

Common causes include:

* a required field is empty;
* a selected channel or role was deleted;
* a field exceeds its allowed length;
* the current server has reached a feature limit;
* Premium is required for the selected option;
* another session changed the same setting while your draft was open.

When another session changed the same setting, review the current server value and apply your change again instead of repeatedly submitting the stale draft.

### Asagi Cannot Send a Message

Check the destination channel and make sure Asagi has:

* **View Channel**;
* **Send Messages**;
* **Embed Links** if the message contains embeds.

If the content intentionally mentions `@everyone`, `@here`, or restricted roles, the bot may also need the corresponding mention permission.

For a DM, the recipient must be able to receive a direct message from Asagi. A user can block bot DMs through their Discord privacy settings.

### Asagi Cannot Assign or Remove a Role

Check all of the following:

* Asagi has **Manage Roles**;
* Asagi's highest role is above the target role;
* the target role still exists;
* the role is not managed by another bot or Discord integration.

The fact that a role was selectable by a dashboard user does not override Asagi's own Discord role hierarchy.

### Auto Moderation Detects a Message but the Punishment Fails

The filter and the punishment use different Discord permissions.

For example:

* deleting requires **Manage Messages**;
* Timeout requires **Moderate Members**;
* Kick requires **Kick Members**;
* Ban requires **Ban Members**.

For member punishments, Asagi must also be high enough in the server role hierarchy.

### A Reminder Did Not Send

Check:

* the reminder is still active;
* the destination channel still exists;
* Asagi can view and send messages there;
* the server timezone is correct.

For recurring reminders, remember that anti-spam protection can skip a delivery when Asagi's previous message is still the latest message in a quiet destination channel.

If the reminder uses Premium-only recurring scheduling, confirm that the server still has Premium.

### An Interactive Message Action Does Not Work

Check the resource used by the action:

* role actions need valid manageable roles and **Manage Roles**;
* channel-message actions need a valid destination channel;
* template-based responses need the referenced template to remain available;
* Anonymous Message actions require Anonymous Messages to be configured.

If the published Interactive Message itself can no longer be updated, make sure its original Discord channel and message are still accessible to Asagi.

### Reaction Roles Do Not Assign a Role

Check that:

* the published Reaction Roles message still exists;
* the configured emoji and role still exist;
* Asagi has **Manage Roles**;
* Asagi's highest role is above the configured role.

If a reaction is mapped to a role that Asagi can no longer manage, the reaction can still appear in Discord while the role action fails.

### Temporary Voice Roles Do Not Update

Check that:

* the configured voice channel or category still exists;
* the configured roles still exist;
* Asagi has **Manage Roles**;
* Asagi is above the temporary roles in the hierarchy.

See [**Members & Roles → In-voice Temporary Roles**](/members-and-roles/in-voice-temporary-roles.md) for target behavior.

### Premium Features Are Locked

Open **Premium → Billing** and confirm that the subscription is active.

Then open **Premium → Bonuses** and make sure the current server has one of your active Premium bonus slots.

A subscription provides bonus slots; it does not automatically enable Premium on every server you manage.

### Music Does Not Start

Check that:

* the server has Premium;
* you are in a voice channel;
* Asagi can **Connect** and **Speak** there;
* Asagi can send messages in the text channel where `/play` was used.

If Asagi reports that no music server is currently available or a source cannot be played, try again later or choose another available result.

### Dashboard Notifications

Some delivery and Discord-action failures are surfaced through dashboard notifications.

Check notifications after a failed role action, message delivery, or other server-side operation. The notification can help identify a deleted resource or missing Discord permission.

### When Contacting Support

Include:

* the **server ID**;
* the Asagi feature or dashboard page;
* the approximate time the problem happened;
* the exact error or dashboard notification, if one appeared;
* the steps needed to reproduce the problem.

Screenshots or a short screen recording are useful when the issue is visual or depends on a specific dashboard workflow.

Do not send passwords, Discord tokens, webhook credentials, or other private credentials.