A command says "The Beacon Events service is switched off in this server."
Why: Beacon Events is switched off for this server. Every Beacon Events command checks this first.
Fix: If you have Manage Server, press the Switch on button under that reply. You can also open the dashboard, pick the server, open Services and switch on Beacon Events, which needs the manager access level. See Set it up.
My event was created but no card appeared in the channel
Why: The bot could not post to the announcement channel: no channel is set, the channel was deleted or the bot cannot post there. Even so, /beacon create saves the event and tells you which of these it is.
Fix: Press Set it up for me on Home if setup never ran. Otherwise, open Settings in the Beacon Events menu and pick an Announcement channel the bot can see. Setup and health on that page says what is wrong. Give the bot View Channel, Send Messages and Embed Links there; the /beacon create reply asks you to check these too. Then open the event and press Post to Discord (or Post to Discord again if it was posted before). Needs you on Home lists every event that is not posted. See Set it up.
Members press Sign Up and get "no longer accepting sign-ups"
Why: The event is not open: it was cancelled or has already completed. A cancelled or completed card also loses its sign-up buttons.
Fix: For a cancelled event whose start time is still ahead, press Open it again on its dashboard page, or run /beacon open with the event number from /beacon list. Either puts the buttons back on the card. For a past event, Copy to a new date opens the editor filled in from it. See /beacon open.
Members press Sign Up and get "Sign-ups are closed"
Why: Sign-ups were closed with /beacon close. The event itself goes on. Members already signed up can still change their status or leave.
Fix: Run /beacon open with the event number from /beacon list to let new sign-ups in again. See /beacon close.
Members see "Signups for this event closed N minutes before the start"
Why: The event has a Sign-up deadline and the deadline has passed. It stops new sign-ups and role changes. Members already signed up can still change their status or leave.
Fix: Open the event in the dashboard editor and change the Sign-up deadline. The member's message tells them to contact the organizer if they want to join.
Members are put on a waitlist and want to join
Why: Either the event or the role, class or spec they picked is full. The bot tells them "⏳ This event is full! You've been added to the waitlist" or names the full role, for example "⏳ Tank is full, so you're on the waitlist."
Fix: Raise the participant cap or the role's cap in the dashboard editor. Saving moves waiting members into the new seats. Promote on the event's waitlist seats one member now: when the event or the member's role is full, the button says so and raises that cap by one, so the card never shows more confirmed than the cap. A seat also frees up when a member leaves or switches from attending to another status. The longest-waiting member whose role has room then moves up on their own and gets a DM. A member can also pick a role that still has room. See /beacon create.
The card's count is lower than the names it lists
Why: The card counts confirmed members only: attending and not on the waitlist. Those are the seats the participant cap and each role's cap count. Tentative and late members are listed with a tag beside their name and do not count. Bench, absent and waiting members have sections of their own.
Fix: Nothing is wrong. A tentative or late member who will come for sure presses Sign Up again. See Set it up.
The organizer got a DM saying the event needs more sign-ups
Why: The event has a Min participants and was still short of it at its warning time. That is 3 hours before sign-ups close unless you picked another time in Settings. Sign-ups close at the start, or at the sign-up deadline when the event has one. The DM goes out once for each start time.
Fix: Share the event to get more sign-ups or lower Min participants in the dashboard editor. To stop these DMs, leave Min participants blank or set it to 0. To change how early the warning comes, use Warn about a short event in Settings.
The form says "I couldn't read that time" or "That time is in the past"
Why: The time must be in the future, written as a day and a time such as 2026-03-10 20:00, tomorrow 8pm or fri 20:00. The day words work in English and in each language the bot speaks, such as morgen, viernes, demain or 金曜日. A time typed without a zone is read in the server timezone, so a time that looks right to you can already be past in that zone.
Fix: Retype it in one of those forms. Add a zone as the last word if it is not the server timezone, for example 2026-03-10 20:00 PST or fri 8pm UTC+2. To change the default zone, set Time zone for events on the Settings page, or the Server timezone on the Server settings tab of the Bot Settings page. See Server timezone.
No reminder arrived
Why: Nobody signed up as attending, tentative or late before the start. A reminder that comes due before anyone has signed up waits and goes out within a minute of the first sign-up. The bot also sends none for a cancelled event. Closing sign-ups with /beacon close does not stop reminders.
Fix: Check that the event is open and has sign-ups. A reminder held back by a cancelled event goes out on the next check after you reopen it, as long as the event has not started.
DM reminders, timing and the default
- A DM reminder skips a member whose DMs are closed. Add a reminder in the dashboard editor if you want one in the channel as well as by DM.
- The bot checks once a minute, so a reminder can arrive up to a minute late.
- Check the Reminder before the start setting for new events. Needs you on Home names a reminder that failed.
An event was marked complete while it was still running
Why: An event ends at its start plus its length, and the bot marks it complete then. The length is the Length picked in the editor, or the Default event length from the Settings page (2 hours unless you changed it).
Fix: For an event that is still running, give it a longer Length in the editor. For events to come, pick a longer Length in the editor, or raise Default event length on the Settings page. For a repeating event, edit its next run: the runs after it keep that length.
A reopened event completed by itself
Why: An open event whose end has passed is marked complete a few minutes later. /beacon open does not change the start time, so an event reopened after its end completes again. A copy made with /beacon clone always starts in the future: the bot refuses a when it cannot read or that has passed.
Fix: For a past event, press Copy to a new date on its dashboard page. It opens the editor filled in from the event a week later, and nothing is made until you save. You can also use /beacon clone with a new when. See /beacon clone.
No recap was posted when an event ended
Why: The recap is off, or the event was never posted to Discord. An event that never had a card gets no recap.
Fix: Turn on Post a recap when an event ends on the Settings page of Beacon Events. For an event that was not posted, press Post to Discord on its dashboard page before it ends.
/poll create says it cannot post in the channel
Why: The bot is missing a permission it needs to post the poll in the channel where you ran the command. The reply names the missing permission.
Fix: Give the bot the permission the reply names in that channel, or run /poll create in another channel. See /poll create.
If the post still fails
- If Discord still refuses the post, or the post fails for another reason, no poll is made. Run the command again.
- A poll made on the Polls page of the dashboard and not posted yet stays there, where you can post it to a channel.
The Discord event was not made
Why: The bot makes the event in your server's Events list only after the card is posted and while the event has not started. It also needs the Create Events permission, and Discord allows 100 scheduled events at a time on a server. Your server's owners and managers get one notice in their dashboard notifications when either stops it. If someone deleted the Discord event, the bot leaves it deleted.
Fix: If the bot lacks Create Events, press + Invite to Server on the Bot page: it gives the bot the permissions its invite asks for, Create Events among them, and removes none. To make room, delete a finished or unused scheduled event in Discord. The event is made within a minute.
The thread under the card was not made
Why: The bot makes the thread once the card is posted, and only with Create Public Threads and Send Messages in Threads in the announcement channel. The server's owners and managers get one notice when it cannot. A card has one thread: if one exists already, the bot uses it.
Fix: Give the bot those permissions in the announcement channel. The thread is made within a minute.
The attendee role was not given
Why: The bot needs Manage Roles, and its own role must be above the attendee role in the role list. A role that belongs to an integration or carries an admin-level permission (such as Administrator, Manage Server, Manage Roles, Ban Members or Kick Members) is never given: pick a plain role. Only members who are confirmed (attending or late) get it, from the start of the event or from the moment they are confirmed, as you chose. An event can pick its own role in the editor, or None, and then the server's role does not apply to it. The server's owners and managers get one notice when the bot cannot give the role.
Fix: In Discord, open Server settings, then Roles, and drag the bot's role above the attendee role. Give the bot Manage Roles. The role is given within a minute.
The automatic voice room is not created
Why: The bot creates the room only for an event that has the automatic voice room turned on, and only with Manage Channels. The room is created 15 minutes before the start, unless you changed Open the room before the start under Voice rooms on the Settings page.
Fix: Turn on the automatic voice room for the event in the dashboard editor. Give the bot Manage Channels, in the category if you picked a Category for voice rooms. The bot also needs it to remove the room afterwards.
When Discord refuses the room
- The server's owners and managers get one notice for the event in their dashboard notifications.
- The bot tries again after 5 minutes, then waits twice as long each time (at most 30 minutes), until 30 minutes after the start.