Troubleshoot common problems

Check accounts, permissions, filters and delivery results before retrying an action.

Start with the server, screen or command, and exact message. A permission issue, an active filter and a connection failure need different fixes.

Sign in again and check the Discord account in the authorization screen. If sign-in loops, check that site cookies are permitted and test without browser extensions. Ask the manager to verify your Discord ID and staff access. An expired invitation needs a new link; it does not replace a valid profile.

Missing page, button or record

Check the current server and your account. Have a manager inspect your panel role, module permissions, department delegations and profile status, then refresh. A high rank alone does not give all rights.

For a missing record, clear search and filters. Look in former members, completed tasks or the module’s archives. Tickets may have category-specific access. For a recently deleted wiki page or report, check trash.

Maintenance, dormant features and restricted beta access are different states; read the displayed explanation. Changing a member role does not reactivate an unavailable feature. A load error should be retried, not interpreted as an empty list.

The bot does not recognize me

Discord membership alone is not staff membership. Have a manager verify your StaffNest profile, Discord ID and imported or mapped staff roles. /setup can help inspect imports, but it does not reinstate removed or blacklisted people.

A temporary service-unavailable message does not necessarily mean your roles are wrong. Check the service status when a broader problem is suspected.

Expired or another person’s menu: run the command again and use your own latest menu.
Insufficient permission: check both Discord and StaffNest rights for the action.
Disabled button: inspect the feature’s availability for the server.
Missing command: check the bot, server and Discord integration permissions, then compare the command reference.
Unconfirmed save: refresh the actual record and use the existing flow’s retry action before creating a duplicate.

Command names remain the registered names in the reference; do not invent translated slash commands.

No channel message or Discord role change

Check that the target channel exists and the bot can view it, send messages and embed links. For tickets, save configuration, run diagnostics, then deliberately publish the opening panel: saving alone does not publish it.

For roles, check Manage Roles and that the bot is above the target role. A panel role does not change Discord’s hierarchy. A record can save even when its Discord effect fails; inspect both results.

No private message

Check Discord’s DM privacy settings, then whether the feature actually sends a DM. Task deadline reminders are panel notifications. The bot’s daily summary must be enabled and only sends useful pending information. Recruitment messages can be directed to the application page instead.

For announcements or meeting invitations, inspect pending, refused and uncertain deliveries. A message with an uncertain result may already have arrived; check before repeating it.

An automation does not run or repeats

Check that the rule is active, inspect execution history and verify exact conditions, permissions and channel. A simulation does not execute actions. New rules save paused. The same follow-up cycle is not alerted on every check. For unexpected repetition, pause the rule and look for equivalent duplicates before reactivating. See automations.

A record changed while I was editing

Preserve any important draft text privately, load the latest version, and reapply only the necessary changes. Do not repeatedly click Save over a concurrent-edit warning.

On mobile, close the navigation menu and scroll the form’s own content to its actions. Tab moves between keyboard controls. If the action remains unreachable, note the device, browser and zoom level. Save your work before accepting a new-version reload.

Ask for help

For an application or internal decision, contact that community’s team. For a StaffNest malfunction, ask your manager to check access and configuration, then contact Discord support with:

Server:
Page or command:
Date, time and timezone:
Steps followed:
Expected result:
Exact message received:
Checks already performed:
Device and browser:
Guide page followed:

Attach a screenshot with unnecessary private information hidden. Never share a password, Discord token, personal sign-in link or configuration secret.