ERMDocs

Common Issues

Solutions to the most frequently encountered problems with ERM.

This page covers the most common issues users encounter with ERM and how to resolve them.

The bot isn't responding

Check these in order:

  1. Is ERM online? — Check ERM's status in your Discord server member list. If the bot appears offline, it may be restarting or undergoing maintenance. Check the ERM Support Server for status updates.

  2. Does ERM have permission to send messages? — Go to your channel permissions and confirm ERM has Send Messages and Embed Links permissions in the channel you're using.

  3. Are slash commands enabled? — Some server configurations disable slash commands for bots. Check Server Settings → Integrations → ERM and ensure commands are enabled.

  4. Are you using the right command? — ERM uses slash commands (type / to see them). Legacy prefix commands are not supported.

"The application did not respond"

This error means Discord sent a command to ERM but didn't receive a reply in time.

  • This is usually a temporary issue caused by high load or a brief outage
  • Wait 30 seconds and try the command again
  • If it persists, check the ERM status in the support server

Commands are missing from the slash menu

  1. Kick ERM from the server and re-invite it
  2. Wait up to 1 hour for Discord to refresh global slash commands
  3. If commands are still missing after 1 hour, report it in the ERM Support Server

"Invalid Permissions" error

You're trying to use a command that requires a higher ERM permission level than your current roles have.

  1. Check the Commands List to see what permission level the command requires
  2. Ask a server Admin to check your role assignments in /config or the dashboard

"Not Permitted" error

The module you're trying to use is either disabled or not fully configured.

  1. Run /config → Basic Settings and verify the module is Enabled
  2. Check that all required channels and roles are set for the module
  3. See Not Permitted for more details

LOA/RA not working

  • Confirm both LOA Role and LOA Channel are set in /config
  • Confirm the module status is Enabled
  • Confirm ERM has Manage Roles permission and its role is higher than the LOA role in the role hierarchy

Shift role not being applied

  • Confirm the on-duty role is set in Shift Management settings
  • Confirm ERM has Manage Roles permission
  • Confirm ERM's role is above the on-duty role in the server's role hierarchy

Dashboard shows "Server not found"

  • Run /setup in your Discord server if you haven't already
  • Log out of the dashboard and log back in with Discord
  • Ensure you have Manage Server permission in the Discord server

API Endpoints

Available ERM API endpoints for shifts, punishments, departments, and guild info.

Missing Channels or Roles

Fix issues where ERM can't find configured channels or roles.

On this page

The bot isn't responding"The application did not respond"Commands are missing from the slash menu"Invalid Permissions" error"Not Permitted" errorLOA/RA not workingShift role not being appliedDashboard shows "Server not found"