Check in the right order
- Are the correct Discord account and server selected?
- Is Spider present and online? Are the module and rule enabled and saved?
- Do the channels, roles and emojis still exist? Can the bot actually use them?
- Do Spider permissions, Discord permissions and hierarchy allow the operation?
- Could an exception, cooldown or schedule explain the lack of action?
- Does the Journal or module history show an error or a result needing review?
Contact Spider support
If the issue continues, join Spider’s Discord using the Support link. Include the module, time, steps, expected result and error message. A focused screenshot helps explain the issue; hide private details unrelated to the request.
Questions and solutions
I am signed out after login
Sign in again with the correct account and check site cookies. Beta, private or maintenance access can be denied independently of Discord permissions. If the issue continues, give support the time and page.
A page stays on Loading
Wait for a result or error, then use Retry. Check the bot connection and revisit the module. Do not repeat a punishment until its actual result has been checked.
Spider does not assign a role
Check Manage Roles, Spider’s role position, the target role and exceptions. Bot, integration and boosting roles cannot be assigned like ordinary roles.
The status is gone but the role remains
Check the removal delay, other rules justifying the role and its origin. Distinguish an empty status from unavailable or offline presence. Review the support-role module diagnostics.
A panel shows an old version
Save settings and republish or synchronise the panel. The dashboard draft and the Discord message already published are separate states.
A button stopped responding
Check that the panel is still active, its channel accessible and Spider online. Some interactions and sessions expire: restart from the current panel.
A direct message is not received
The member may block server direct messages. Review the action status and delivery history; a missing DM does not prove that the punishment or welcome failed.
Automatic reactions are missing
Test a new message matching the filters. Check Add Reactions, channel access, the chosen emoji and custom emoji restrictions.
Starboard does not publish a message
Check the correct emoji, eligible reaction count, exceptions, source channel and destination permissions. Manually deleted publications are not automatically recreated.
A sticky message appears late
Check the trigger message count, delay and cooldown. These settings prevent constant reposting in busy channels.
A custom command is missing
Check that it was published, its name is valid and publication did not fail. Role and channel conditions and Discord command settings also affect access.
A status invite is not recognised
Check that it is valid and belongs to the server. Personal invite mode also needs an identifiable creator. An unknown or inaccessible code is not a confirmed match.
An embed image is not displayed
Use an image URL accessible without signing in. Check Embed Links and the publication preview. A web page containing an image is not always a direct image URL.
Statistics are empty or incomplete
Choose a tracked period and check channel filters and timezone. Untracked periods are not reconstructed; unavailable information does not mean zero activity.
A ticket or position is inaccessible
Check required and excluded roles, handling teams, dates, opening limits and cooldowns. For the Support centre, also check its linked ticket panel and choice.
A personal voice channel does not appear or stays empty
Check the entry channel, target category, Manage Channels and Move Members. Review history after an error; category permissions can prevent moving a member even when the channel was created.
Changing website language does not change bot replies
Website language is a personal preference. Configure the bot language in General for the relevant server. Custom text is not automatically translated.