Troubleshooting

Find the symptom below, then check the setting that usually fixes it.

I set something up, but nothing happens

Check that the module is on, the setting was saved or published, and the chosen channel is still available to Guardy. Then test the exact member action that should start the feature. For example, open the ticket panel, join with a test account, or send an eligible message.

I cannot find a Guardy command

Make sure Guardy is still installed, the related module is on, and your account is allowed to use app commands in that channel. Close and reopen Discord if the slash-command list has not refreshed.

Guardy cannot post, react, or create a ticket

Open the selected Discord channel and check its permissions. Guardy must be able to see the channel and do the action you chose, such as sending messages, adding reactions, attaching files, or managing a channel or thread.

Guardy cannot give or remove a role

Move Guardy's role above the role it should manage, then check that it has permission to manage roles. Discord will not let Guardy change roles or members above its highest role.

It works for an owner but not for members or staff

Test with a normal member and a non-owner staff account. Owners can bypass restrictions that still affect everyone else. Check the channel permissions, the module's staff access, and Discord's role order.

Still stuck?

Write down the server name, feature, action you tried, what you expected, what happened, and the exact Discord error. Then read that feature's guide or contact support.