Docs / Core Services / Social Feeds / Troubleshooting
Built in

Social Feeds: Troubleshooting

In short

Fixes for feeds that switched themselves off, alerts that do not post, greyed out Twitch and Kick tiles and feeds that will not save.

A feed switched itself off

Why: After 5 failed checks in a row, a feed turns itself off and shows its last error on its Overview tile. The usual causes are a deleted channel, or a bot that lost View Channel, Send Messages or Embed Links in it.

Fix: Fix the channel or the bot's permissions, then press Reset ("Clear failures + re-enable") on the tile. Press Skip to current first if you do not want a backlog of old items posted. See Set it up.

Who is told

The server's owner and managers get a dashboard notification, at most once a calendar month for the same feed.

A new feed posted nothing

Why: A new feed does not post its backlog. The first check only marks the newest item as seen, and posting starts with the next new item.

Fix: Press Test (posts for real) on the Overview tile to post the newest item that passes the filters now. Then check the Poll interval (seconds) and the two keyword filters. The tile shows "nothing posted yet" and the "next poll" time.

Poll interval and keyword filters
  • Checks also run on the poll interval, for example every 900 seconds for YouTube and RSS.
  • Keyword filters can hide an item too: "Only post if it mentions" and "Never post if it mentions" search the title, the item text and the link. An exclude match always wins.
  • When the filters block every recent item, Test answers "All {n} recent items were blocked by this feed's keyword filters. Nothing to post."

The Twitch or Kick tile is greyed out

Why: Twitch and Kick alerts need app credentials that the platform holds; without them, the tile is greyed out and cannot be clicked. The hosted bot has no Kick app credentials, so Kick alerts do not work on it.

Fix: Use another source, such as a YouTube Channel or Generic RSS / Atom feed. Nothing on your side turns the tile on.

The notice above the tiles

When the credentials are missing, a notice above the tiles says so. For Kick it reads "Kick alerts need Kick app credentials on the bot. Ask the platform owner to add them."

A stream alert did not post

Why: An alert posts when a check finds the stream live. It can be late by up to the "Poll interval (seconds)" (120 seconds by default) plus half a minute.

Fix:

  • Check the tile is on and has no error.
  • Clear or correct Only alert for these games: names are matched as the platform shows them, ignoring case.
  • Check the keyword filters and the Digest.
  • Go live and wait one poll interval, or lower the interval (the minimum for Twitch and Kick is 60 seconds).
Everything that stops an alert
  • The stream was not live when the check ran.
  • The stream was already live when you added the feed. The first check only marks that stream as seen.
  • A game filter is set ("Only alert for these games") and the stream started in another game.
  • The keyword filters block it.
  • A Digest is set, so the alert waits for the next digest message.
  • The feed is switched off or failing.

When the streamer is offline, the Test (posts for real) button answers "Source returned no items for {label} (e.g. streamer offline or no recent patches). Nothing to post."

The live role is not given to the streamer

Why: The feed needs both a Live role and the Streamer's member id, and the bot has to be able to give that role.

Fix: Turn on Developer Mode in Discord's Advanced settings, right-click the member and choose Copy User ID, then paste it into Streamer's member id. Move the bot's role above the live role. The Setup check shows what the bot lacks.

When the role cannot be given
  • Without the id the form says "Enter the streamer's member id to use a live role." The id must be a Discord user ID, digits only.
  • The bot cannot give a role that sits above its own highest role or that Discord manages. It cannot give one at all when it lacks Manage Roles.
  • If the member is not in the server, the role is not given.

Test says "Discord post failed"

Why: The bot could not post to the channel. The message reads "Discord post failed. Check the channel permissions and that the bot is in the server."

Fix: Give the bot View Channel, Send Messages and Embed Links in that channel, plus Manage Webhooks if the feed posts as a webhook. Or edit the feed and pick another channel.

When the source cannot be read

When the feed's source cannot be read, the message reads "Source fetch failed:" followed by the reason. Check the username, channel or URL on the feed.

The feed will not save

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

Fix: Correct the field the message names. Delete feeds you no longer use to make room under the limit.

What each message means
  • "That channel is not in this server": pick a text channel, an announcement channel or a forum of this server.
  • "Channel required": no channel was chosen.
  • "Template does not render:" followed by the reason: the "Message text (optional)" has a brace the bot cannot read, such as a lone { or }. A literal brace is written as {{ or }}. A name in braces that is not a placeholder is not refused: it is posted as written.
  • "The bot needs Manage Webhooks in that channel to post as a webhook. Give it the permission or choose Post as bot."
  • A refusal that gives the limit (100) and how many feeds the server already has. Every feed counts, on or off.
  • "Live refresh must be a number of seconds, at least 120.": the box does not hold a number.

Nothing is checked after switching Social & Patches off and on

Why: While the service is off for a server, its feeds are not checked and each one is set aside for an hour at a time. After you switch the service back on, a feed can wait up to an hour for its next check.

Fix: Press Disable and then Enable on the feed's tile, or open Edit and click Save Changes. Either puts the feed back on the next pass. To post the newest item that passes the filters now, press Test (posts for real).

Items stop being published to followers

Why: In an announcement channel, "Publish to followers" publishes each post the bot makes, and Discord allows 10 per hour per channel. Over that, the item still posts and only the publish is skipped.

Fix: Wait for the hour to pass, or lower how many items a channel receives with the keyword filters or a Digest. For a feed that posts as a webhook, set Post as to the bot: posts made as a webhook and Test posts are never published.

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