Bot permissions
Most “tickets aren’t created” issues come down to permissions. Confirm the bot can create and edit channels/threads in the target location.
- Check category-level overrides
- Ensure the bot role is above roles it must manage
- Validate thread permissions if using thread mode
Commands not showing
Slash commands can take a few minutes to propagate. If they never show:
- Re-invite the bot with
applications.commands. - Confirm the bot can send messages in the channel you’re testing.
- Try in a different channel where the bot has permissions.
Tickets not creating
Use this checklist:
- Verify the form panel is published to the correct channel.
- Confirm the ticket category exists and is not full (Discord has limits).
- Check whether an automation rule is closing tickets immediately (dry run your rules).
Tip
If you’re stuck, temporarily disable automations to isolate permission vs workflow issues.
Webhooks failing
- Verify your endpoint returns
2xxquickly (under 3 seconds). - Verify signatures using the raw request body.
- Use idempotency on event ids to handle retries.
API 401/403
401 means missing/invalid token. 403 means the token is valid but lacks the required scope or workspace access.
Note
A common issue is using an agent token to call admin-only endpoints (webhooks, security settings).
Keyboard shortcut (if enabled): ⌘ + K opens quick navigation.