Docs / Core Services / Analytics / Troubleshooting
Built in 24 commands 6 settings

Analytics: Troubleshooting

In short

Fixes for Analytics commands that refuse to run, charts that look short, members missing from rankings, counters that stay still and role rewards that do not land.

A command says "The Analytics service is switched off in this server."

Why: Analytics is switched off for this server. While it is off, the bot refuses every Analytics command with a private reply.

Fix: If you have Manage Server, press the Switch on button under that reply. You can also open your server's Services page in the dashboard and switch Analytics on. Then run the command again. See Set it up.

A chart or ranking shows fewer days than I asked for

Why: The window never reaches past what the server keeps. On a server that keeps 30 days of data, a 90-day request shows 30 days, and the reply says "Showing 30 days: this server keeps 30 days of Analytics data."

Fix: Raise Keep data for on the Analytics Settings page (30, 90, 180 or 365 days). Detail older than the window is removed every night.

A member does not show up on /stats, /user or /chart member

Why: The bot refuses with a private reply when the member:

  • hid their card ("That member has hidden their stats card.")
  • is a bot account while Leave bots out is on
  • holds an excluded role and has nothing stored

Fix: Ask the member to press the Show my card button on /me to show their card again. For bots or excluded roles, check Leave bots out and Roles to leave out on the Analytics Settings page.

A member is missing from /leaderboard or /top

Why: Bot accounts never appear on member rankings. Members who currently hold an excluded role are left out too, including their earlier activity.

Fix: Check Roles to leave out on the Analytics Settings page. A role change is picked up within half an hour.

If voice time looks short

Voice rankings skip a session the bot had to close on its own after missing the leave.

Messages from a channel are not counted

Why: Messages in excluded channels, and in threads and forum posts under them, are not recorded. Channels excluded before the setup wizard ran were also left out of the history import.

Fix: Remove the channel from Channels to leave out on the Analytics Settings page. New messages are counted from then on; messages sent while it was excluded stay uncounted.

A counter channel name does not change

Why: The bot renames a counter every 6 minutes, and only when the number changed. It also cannot rename a channel unless it has Manage Channels, can see the channel and, for a voice channel, can connect to it.

Fix: Run /counter check. It lists privately what is wrong, one line per counter channel. For a voice channel you made yourself, allow the bot Connect on it.

Counters that need more
  • Online, playing and streaming counters need the Presence intent.
  • A ban counter needs Ban Members.

Online or Playing numbers read zero or offline

Why: Without the Presence intent, Discord sends no presence, so every member reads as offline. Status and activity tracking stay off too.

Fix: Turn the Presence intent on in the Discord Developer Portal and on the bot's settings page. /counter check says when it is missing.

/counter setup says all counter channels are in use

Why: A server has up to 10 counter channels, and every slot is taken. The bot replies that all counter channels are in use and asks you to delete one.

Fix: Delete a counter you no longer need with /counter delete, then run /counter setup again.

A role reward is not given

Why: The bot refuses a reward in these cases:

  • The bot is missing Manage Roles.
  • The reward role is managed by an integration, such as a bot or Nitro booster role.
  • The role sits at or above the bot's highest role.
  • The role carries a privileged permission such as Administrator, Manage Server, Manage Roles, Manage Channels, Ban, Kick, Manage Webhooks or Mention Everyone.

Fix: Read the warning on the reward on the Role rewards page. In Discord, give the bot Manage Roles and drag its role above the reward role in Server Settings, Roles. Pick a different role if it holds a privileged permission.

/invites says some joins could not be traced

Why: The bot reads your server's invites to see which one a member used. Without the Manage Server permission it cannot, so those joins are not credited to anyone.

Fix: Give the bot Manage Server in Discord. See /invites.

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