Docs / Core Services / Announcements / Troubleshooting
Built in 3 commands

Announcements: Troubleshooting

In short

Fixes for announcements that did not post, show a channel tag, will not save, ping the wrong people or post at the wrong hour.

An announcement did not post

Why: Announcements is switched off for the server, or the entry is paused. A post can also be up to half a minute late, because the bot checks for due announcements every 30 seconds.

Fix: Switch on the Scheduled Announcements card on the Services page if it is off. Then look at the Announcements page: a waiting entry shows under Pending, and a Paused one never posts until you press Resume. See Set it up.

While the service is off

If Announcements is switched off for the server, due announcements are skipped and stay waiting until you switch it back on. They are not failed or deleted.

An entry shows CHANNEL DELETED or NO ACCESS

Why: The bot cannot post in that announcement's channel: the channel was deleted, the bot cannot see it or it cannot post there.

Fix: Click Edit, pick a channel that works and save. Or give the bot View Channel and Send Messages in the old channel, plus Embed Links if the announcement has embeds. The tag clears by itself on the next post that reaches the channel.

What happens to the post
  • The bot looks the channel up before each post. When it is gone, hidden from the bot or in another server, the post is skipped. A one-time announcement then moves to Failed, and a repeating one keeps its schedule and skips that slot.
  • When the bot can see the channel but cannot post in it, the post is sent and Discord refuses it. The NO ACCESS tag appears afterwards, and a one-time announcement ends as completed, not failed.
  • The server's owner and managers get a dashboard notification, at most once a calendar month for the same channel.
Failed and completed announcements
  • A failed one-time announcement is re-armed by your save and posts at its "Send at" time, right away if that time has passed. Check it before you save.
  • A completed one cannot be edited: fix the channel and schedule it again.

The page says "Some announcements cannot be delivered"

Why: At least one waiting, paused or failed entry carries a CHANNEL DELETED or NO ACCESS tag. The banner reads "Some announcements cannot be delivered. The channel was deleted or the bot lost access. Edit the announcement and pick a new channel."

Fix: Edit each tagged entry and pick a working channel, as above.

The dashboard will not let me save an announcement

Why: The dashboard refused the save with a short red message that names the problem.

Fix: Correct the field the message names, then click Schedule again (Save changes when you edit). The form opens again without what you typed, so keep a copy of a long message.

What each message means

The first two show on the Announcements page, the others at the top of the form.

  • "manager role required": your dashboard role does not have Edit on Scheduled Announcements.
  • "too many pending announcements (max 100)": the server already has 100 announcements under Pending. Paused ones do not count. To make room under the 100 limit, cancel or pause Pending ones.
  • "invalid timezone", "invalid channel" or "channel not in this server": the zone name is not valid, or the channel is not one of this server's channels.
  • "message too long": the message is over 2000 characters.
  • "invalid embeds JSON": the embed box must hold one JSON object or a list of objects.
  • "message or embed required": the message holds only spaces and there is no embed.
  • "invalid datetime": the date for a one-time post could not be read.
  • "could not schedule": no next post time could be worked out for the repeating schedule.

Nobody was pinged by the announcement

Why: A box under Mentions is off, or Discord's own rule blocked the ping. Discord pings a role only when it is mentionable or the bot has Mention @everyone, @here and All Roles.

Fix:

  • Write the role as a role mention (<@&ROLE_ID>) in the Message box and keep "Allow role mentions" on.
  • Make the role mentionable in Discord, or give the bot Mention @everyone, @here and All Roles.
  • To ping everyone, schedule the post on the dashboard, check "Allow @everyone / @here" and give the bot that permission in the channel.

The Setup check warns about both.

Who a post pings
  • A scheduled post pings roles and users, but not @everyone or @here, unless you checked "Allow @everyone / @here".
  • With "Allow role mentions" turned off, the role name shows but nobody is pinged.
  • Posts made with /announce now never ping @everyone or @here.
  • @everyone and @here need the Mention @everyone, @here and All Roles permission too.

The announcement posted at the wrong hour

Why: Each announcement keeps the timezone it was saved with. Changing your Server Timezone later does not move existing announcements.

Fix: Click Edit on the announcement and change its Timezone field. Before you click Save changes, check "Send at" on a one-time announcement or "End date" on a repeating one. See Server Timezone.

/announce says I need Manage Server

Why: Only the server owner, members with Manage Server or Administrator and the roles or members you allowed on the Commands page can run /announce. Discord still lists the command for every member.

Fix: Allow the role under Services, Scheduled Announcements, Commands. See /announce now.

The reply and Command Access rules
  • Anyone else gets "You need Manage Server or a role allowed on the dashboard's Commands page to use this command."
  • Command Access rules are checked first, so a member a rule refuses gets that rule's message instead.

/announce now says the service is switched off

Why: Announcements is switched off for the server. The bot answers "The Scheduled Announcements service is switched off in this server."

Fix: If you have Manage Server, press the Switch on button under that reply. You can also switch on the Scheduled Announcements card on the Services page.

Setup shows an error

Why: Discord refused to create the #announcements channel. The bot is missing a permission, or Discord is limiting requests.

Fix: Give the bot's role the permission named, or wait a moment if Discord is rate limiting. Then press Run Setup again: running it twice is safe, because an existing channel is left untouched. The Setup check shows what else the bot lacks.

What the Setup page says

The Setup button on the Announcements page opens the Setup page. There, Run Setup (Re-run Setup once a channel is found) creates the #announcements channel.

When The page says
Discord refuses with a permission error "The bot is missing Manage Channels or Manage Roles in this server. Grant them and run setup again."
Discord is limiting requests "Discord is rate limiting us. Wait a moment and run setup again."
The guide is posted but cannot be pinned "Setup complete.", and the guide stays unpinned
To pin the guide

Setup does not post the guide again in a channel that exists. To pin it, give the bot Pin Messages and pin the guide yourself in Discord.

Still stuck? Run /yourbot check in your server first: it lists every permission and setting the bot is missing. Then ask in our Discord with what you tried. Ask in Discord
Was this page helpful?
YourBot docs Reference tables are generated from the code that is running. Ask in Discord