Error Codes FAQ

Common Discord API errors and how to fix them

All Invalid Form Body Moderation Not Found Permissions Rate Limits Server Error Tickets

Missing Permissions Error 50013 HTTP 403

Permissions

The bot doesn't have sufficient permissions to perform this action.

Solution

Move the 'Scrapline' role (or your allocated bot role) above the target role in Discord's role hierarchy. The bot role must be higher than any role it needs to manage.

  1. Go to Server Settings → Roles
  2. Drag the bot's role above the roles it needs to manage
  3. Ensure the bot role has the required permissions enabled
  4. Check channel-specific permission overrides

Common Causes

  • Bot role is below the role it's trying to manage
  • Bot doesn't have the required permission enabled in server settings
  • Channel-specific permissions are blocking the bot

Unknown Channel Error 10003 HTTP 404

Not Found

The channel was deleted, doesn't exist, or the bot can't access it.

Solution

Re-select the channel in the dashboard or recreate it if it was deleted.

  1. Go to your server dashboard
  2. Navigate to the relevant module (Verification, Tickets, etc.)
  3. Re-select the channel from the dropdown
  4. Save your changes

Common Causes

  • Channel was deleted
  • Bot was removed from the server and re-added
  • Channel permissions changed
  • Channel ID is incorrect

Unknown Guild Error 10004 HTTP 404

Not Found

The server (guild) doesn't exist or the bot is no longer in it.

Solution

Re-invite the bot to your server using the invite link.

  1. Go to the invite page
  2. Select your server
  3. Ensure the bot has the required permissions
  4. Complete the invite process

Common Causes

  • Bot was removed from the server
  • Server was deleted
  • Bot invite expired

Unknown User Error 10007 HTTP 404

Not Found

The user doesn't exist, left the server, or the bot can't see them.

Solution

The user may have left the server. Check if they're still a member.

  1. Verify the user is still in your server
  2. Check if the user was banned or left
  3. Try the action again with a different user

Common Causes

  • User left the server
  • User was banned
  • User account was deleted
  • Bot can't see the user due to permissions

Cannot Send Messages to This User Error 50007 HTTP 403

Permissions

The bot cannot send a direct message (DM) to this user. Common when the user has DMs disabled or has blocked the bot.

Solution

The moderation action may still have been applied (for example, a mute). The user will not receive a DM. Ask them to enable DMs from server members or to unblock the bot if they want to receive notifications.

  1. The mute/ban/kick still applies; only the DM failed
  2. To allow DMs: User Settings → Privacy & Safety → Allow direct messages from server members
  3. User can unblock the bot if they previously blocked it

Common Causes

  • User has DMs disabled for this server
  • User has blocked the bot
  • User has disabled DMs from everyone

Missing Access Error 50001 HTTP 403

Permissions

The bot doesn't have access to the resource (channel, role, etc.).

Solution

Ensure the bot has access to the channel or role. Check channel permissions and role hierarchy.

  1. Check channel permissions for the bot
  2. Verify the bot role is high enough in the hierarchy
  3. Add the bot to private channels if needed

Common Causes

  • Channel is private and bot isn't added
  • Role is above the bot's role
  • Channel permissions deny access

Invalid Form Body Error 50035 HTTP 400

Invalid Form Body

The request data is invalid or malformed.

Solution

Check the data being sent. This usually indicates a bug in the bot or dashboard.

  1. Try the action again
  2. If it persists, contact support
  3. Check Discord's status page for API issues

Common Causes

  • Invalid data format
  • Missing required fields
  • Data exceeds Discord's limits

Too Many Requests HTTP 429

Rate Limits

You've exceeded Discord's rate limit. Wait before trying again.

Solution

Wait a few seconds and try again. Rate limits reset automatically.

  1. Wait 1-5 seconds
  2. Try the action again
  3. For bulk operations, space them out over time

Common Causes

  • Too many requests in a short time
  • Bulk operations (banning many users)
  • Rapid command usage

Internal Server Error HTTP 500

Server Error

Discord's API is experiencing issues.

Solution

Wait a moment and try again. Check Discord's status page if issues persist.

  1. Wait 30-60 seconds
  2. Check https://discordstatus.com
  3. Try again after Discord resolves the issue

Common Causes

  • Discord API outage
  • Temporary Discord server issues
  • Discord maintenance

Invalid OAuth2 Access Token Error 50025 HTTP 403

Permissions

The OAuth token is invalid or expired.

Solution

Re-authenticate by logging out and logging back in.

  1. Log out of the dashboard
  2. Log back in with Discord
  3. Try the action again

Common Causes

  • Token expired
  • Token was revoked
  • User changed password

Invalid Webhook Token Error 50027 HTTP 403

Permissions

The webhook token is invalid or the webhook was deleted.

Solution

Recreate the webhook or update the webhook URL in settings.

  1. Go to Server Settings → Integrations → Webhooks
  2. Create a new webhook or update the existing one
  3. Update the webhook URL in your bot settings

Common Causes

  • Webhook was deleted
  • Webhook token changed
  • Invalid webhook URL

Ticket Close Log Not Delivered Error SCP-TKT-01 HTTP N/A

Tickets

A ticket was closed, but the 'Ticket Closed' log embed couldn't be delivered because this server has no valid mod-log channel configured.

Solution

Set a mod-log channel in the dashboard under Audit Logs, or disable the Audit Logs feature if you don't want ticket close logs.

  1. Open your server dashboard → Configure → Moderation
  2. Open the Audit Logs card and pick a Mod Log channel from this server
  3. Save your changes
  4. Close a test ticket to confirm the log arrives

Common Causes

  • No mod-log channel has been configured for this server
  • The configured mod-log channel was deleted
  • The configured channel ID belongs to a different server
  • The bot can't see the configured channel

Ticket Transcript Not Delivered Error SCP-TKT-02 HTTP N/A

Tickets

Transcripts are enabled with a channel destination, but no valid transcript channel exists in this server, so the transcript wasn't posted.

Solution

Pick a transcript channel in the Tickets configuration, or switch the transcript destination to DM-only.

  1. Open your server dashboard → Configure → Panels & Embeds → Tickets
  2. Set the Transcript Channel to a channel in this server
  3. Save your changes
  4. Close a test ticket to confirm the transcript arrives

Common Causes

  • No transcript channel has been configured
  • The transcript channel was deleted
  • The configured channel ID belongs to a different server
  • No mod-log channel exists to fall back to

Bot Cannot Create Ticket Channels Error SCP-TKT-03 HTTP 403

Tickets

A member clicked a ticket button but the bot doesn't have permission to create the ticket channel or category.

Solution

Give the bot Manage Channels permission and make sure its role sits above the ticket category in the role hierarchy.

  1. Go to Server Settings → Roles and give the bot Manage Channels
  2. Check the ticket category's permission overrides include the bot
  3. Ask the member to click the ticket button again

Common Causes

  • Bot is missing the Manage Channels permission
  • Bot's role is below the ticket category's permission requirements
  • Category permission overrides block the bot

Ticket Creation Failed Unexpectedly Error SCP-TKT-04 HTTP N/A

Tickets

Ticket creation failed for a reason other than permissions (rate limits, deleted category, Discord outage).

Solution

Try again in a minute. If it keeps happening, re-select the ticket category in the dashboard and check Discord's status page.

  1. Wait a minute and try the ticket button again
  2. Open your dashboard → Tickets and re-save the ticket category
  3. If the issue persists, contact support with this error code

Common Causes

  • The ticket category was deleted mid-flow
  • The server hit Discord's channel limit (500)
  • Temporary Discord API outage or rate limit

Mute Command Failed Error SCP-MUTE HTTP 403

Moderation

The /mute command failed. This usually means the bot cannot assign the Muted role or create it.

Solution

Give Scrapline a role with Administrator (or at minimum: Manage Roles) and drag it above the Muted role and above the target member's highest role in Server Settings → Roles.

  1. Go to Server Settings → Roles
  2. Drag the Scrapline role above the Muted role
  3. Ensure Scrapline's role has Manage Roles (or Administrator) enabled
  4. If Muted doesn't exist, the bot will create it. Ensure it has Create Role permission
  5. Try the mute command again

Common Causes

  • Bot role is below the Muted role in the hierarchy
  • Bot role is below the member being muted
  • Bot lacks Manage Roles permission
  • Bot lacks Create Role permission (when creating Muted for the first time)

Missing Permissions (Mute/Warn/Kick/Ban) Error 50013 HTTP 403

Moderation

The bot lacks permission to perform the moderation action. For mutes, the bot needs Manage Roles and a role higher than both the Muted role and the target.

Solution

Move the Scrapline role above the Muted role (and above members you want to mute). Grant Manage Roles and, for creating Muted, Create Role.

  1. Server Settings → Roles → drag Scrapline above Muted
  2. Right-click Scrapline's role → Edit → enable Manage Roles
  3. For first-time setup: enable Create Role so the bot can create the Muted role

Common Causes

  • Bot role is below the Muted role
  • Bot role is below the target's highest role
  • Manage Roles is disabled for the bot