Moderation Errors
These are the moderation-related errors that can appear while using commands, context menus, automations, and moderation pages in the dashboard.
Discord Command and Context Menu Errors
"This command can only be used in a server."
What happened: A moderation slash command was used outside a Discord server. What to do: Run the command inside the server where moderation is enabled.
"Moderation tools can only be used inside a server."
What happened: A moderation context menu or modal action was triggered outside a valid server context. What to do: Reopen the action inside the target server and try again.
"Moderation tools are not enabled for this server."
What happened: The server has not enabled moderation in Nexcord. What to do: A server admin should enable moderation in Moderation Settings first.
"Moderation is not enabled for this server."
What happened: A moderation context flow was started, but the moderation module is disabled. What to do: Ask a server admin to enable moderation in the dashboard before trying again.
"You don't have permission to warn members."
What happened: Your moderator role is not allowed to use the warn action in Nexcord. What to do: Ask a server admin to grant your role Warn permission in Moderation Settings.
"You don't have permission to mute members."
What happened: Your moderator role is not allowed to use the mute action in Nexcord. What to do: Ask a server admin to grant your role Mute permission in Moderation Settings.
"You don't have permission to kick members."
What happened: Your moderator role is not allowed to use the kick action in Nexcord. What to do: Ask a server admin to grant your role Kick permission in Moderation Settings.
"You don't have permission to ban members."
What happened: Your moderator role is not allowed to use the ban action in Nexcord. What to do: Ask a server admin to grant your role Ban permission in Moderation Settings.
"You don't have permission to unban members."
What happened: Your moderator role is not allowed to use the unban action in Nexcord. What to do: Ask a server admin to grant your role Unban permission in Moderation Settings.
"You don't have permission to moderate members."
What happened: Your role does not have any allowed moderation actions in Nexcord. What to do: Ask a server admin to add your role under Moderator Roles and enable the actions you need.
"You don't have permission to $ members."
What happened: The context menu flow reached a specific action that your role is not allowed to use. What to do: Ask a server admin to enable that exact action for your moderator role.
"Invalid duration. Use format: 10m, 1h, 7d (max 28d)"
What happened: A mute duration was entered in the wrong format or above the maximum allowed length.
What to do: Use a format like 10m, 1h, or 7d, and keep the timeout at 28 days or less.
"You cannot moderate bots."
What happened: The context menu target was a bot account. What to do: Choose a human member instead. Nexcord does not allow moderation actions against bots through that flow.
"That member is no longer available."
What happened: The selected member left the server or could not be resolved before the action finished. What to do: Refresh the member list and try again only if the member is still in the server.
"I can't moderate this member — they have a higher role than me."
What happened: Nexcord's bot role is below the target member's highest role. What to do: A server admin should move the bot role higher than the roles it needs to moderate.
"Something went wrong. Please try again."
What happened: A moderation command or context menu action failed for a general reason. What to do: Try the action again once. If it keeps failing, ask a server admin to check the module setup and bot permissions.
"Something went wrong. Please try again in a moment."
What happened: A moderation interaction failed in Discord and did not match a more specific error. What to do: Wait a moment and try again.
Moderation API and Settings Errors
"Insufficient permissions"
What happened: The dashboard request was made by a user who is not allowed to manage moderation settings or logs. What to do: Sign in with a server admin account or ask a server admin to make the change.
"Failed to update moderation settings"
What happened: Nexcord could not save the moderation module settings. What to do: Try saving again. If the error continues, refresh the page and retry.
"discord_role_id and discord_role_name are required"
What happened: A moderator role request was submitted without a valid role selection. What to do: Pick a Discord role first, then submit the change again.
"Failed to save moderator role"
What happened: Nexcord could not add or update the selected moderator role in the database. What to do: Try again after refreshing the role list. If it still fails, confirm the role still exists in Discord.
"Failed to update automation"
What happened: The automation builder could not save the current workflow. What to do: Review the workflow, save again, and make sure the automation still exists.
"Automation not found"
What happened: The automation being edited or deleted no longer exists. What to do: Refresh the automations page and reopen the remaining workflow list.
"Failed to load moderation logs"
What happened: Nexcord could not load the moderation log data for the server. What to do: Refresh the page and try again. If it keeps happening, try again later in case the logs service is temporarily unavailable.
Note: The following errors are plan-limit errors. Fixing them may require a server admin to upgrade the server to Nexcord Pro.
"Upgrade to Pro for unlimited automations"
What happened: The server is on the Free plan and has reached the automation limit. What to do: Delete an existing automation or ask a server admin to upgrade the server to Pro.
"DM User node requires Pro"
What happened: The automation uses a DM action that is only available on Pro. What to do: Remove the DM node or upgrade the server to Pro.
"Upgrade to Pro to view member history"
What happened: Member moderation history lookup is only available on Pro. What to do: Ask a server admin to upgrade the server if you need member history lookup.
Dashboard Errors
"Failed to load settings."
What happened: The dashboard could not load the moderation page's initial server data. What to do: Refresh the page and try again. If the server was removed or access changed, ask a server admin to verify your access.
"Failed to load moderation settings."
What happened: The moderation settings page could not load its saved configuration. What to do: Refresh the page and try again.
"Please wait 60 seconds before refreshing again."
What happened: You refreshed channels or roles too quickly from the dashboard. What to do: Wait one minute before trying the refresh button again.
"Failed to refresh channels. Please try again."
What happened: The dashboard could not refresh the latest Discord channel list for moderation settings or logging settings. What to do: Try the refresh button again after a short wait. If it still fails, confirm the bot is still in the server and has access.
"Failed to refresh roles. Please try again."
What happened: The dashboard could not refresh the latest Discord role list for moderation settings. What to do: Try the refresh button again after a short wait. If it still fails, confirm the bot is still in the server.
"Failed to save moderation settings."
What happened: The moderation settings page could not save the current module configuration. What to do: Try again once. If it keeps failing, reload the page and reapply the change.
"Select a role first."
What happened: You tried to add a moderator role without selecting a Discord role first. What to do: Choose a role from the dropdown, then click the add button again.
"Failed to add moderator role."
What happened: The selected moderator role could not be added from the dashboard. What to do: Refresh the role list and try again.
"Failed to remove moderator role."
What happened: The dashboard could not remove the selected moderator role. What to do: Refresh the page and try the removal again.
"Failed to update moderator role."
What happened: Nexcord could not save the permission toggles for that moderator role. What to do: Try the toggle again. If it keeps failing, reload the page first.
"Something went wrong, please try again."
What happened: Quick Setup in moderation settings failed while trying to grant full access to selected roles. What to do: Recheck the selected roles and try the Quick Setup action again.
"Failed to load mod logs."
What happened: The moderation logs page could not load the log list. What to do: Refresh the page and try again.
"Failed to load member history."
What happened: The member history drawer could not load the selected user's history. What to do: Try again with the same user ID. If the server is on the Free plan, Pro may be required for this feature.
"Failed to load automations."
What happened: The automation builder page could not load saved workflows or related data. What to do: Refresh the page and try again.
"Failed to create automation."
What happened: The new automation could not be created. What to do: Try again after checking that you have not reached your automation limit.
"Failed to delete automation."
What happened: The selected automation could not be deleted. What to do: Refresh the page and try the delete action again.
"Failed to save automation."
What happened: Changes to an automation workflow could not be saved. What to do: Review the workflow and save again.
"Only one trigger allowed per automation"
What happened: The builder only supports one trigger node per automation. What to do: Remove the extra trigger and keep a single starting trigger in the workflow.
Note: The following dashboard error is a plan-limit error.
"Upgrade to Pro to use the DM User node"
What happened: The dashboard builder blocked a Pro-only automation node on the current plan. What to do: Remove the DM node or ask a server admin to upgrade the server to Pro.