The birthday role was not given or not removed

If the birthday role was not given or is still on a member after their birthday, check the role warning on Birthdays first. Birthday Bot needs permission to manage the selected role, and the member's birthday must qualify under the server's rules.

On the website

1. Open Birthdays and check Birthday role.
2. Open its permission warning, if shown, and follow the fix in Discord.
3. Open Overview and press ↻ Re-check after changing permissions.
4. If there is no permission problem, check the member's eligibility and birthday clock below.

What success looks like

Eligible members receive the chosen role during their birthday, and the bot removes it when their birthday has ended. Which clock decides that is the Timezone choice on Birthdays: the member's own, or the server's. The role check follows the birthday date, separately from the message's post hour.

No birthday role is selected

Check: Look at Birthday role on Birthdays.

Fix: Choose a role dedicated to birthdays and press Save changes. Do not use a general member role: Birthday Bot removes its birthday role from everyone who is not being celebrated that day. A role that 100 or more members already hold cannot be chosen, in the picker or in the command, for that reason. A role that grows past that number after it was chosen keeps working. Set up birthday celebrations explains the setup.

The role is above Birthday Bot

Check: Open the role warning and look for Role too high.

Fix: In Discord's Server Settings, open Roles and move Birthday Bot's role above the selected birthday role. Then re-check on the website. Missing permissions explains role warnings.

Birthday Bot lacks Manage Roles

Check: Look for Manage Roles under Missing in the warning.

Fix: Follow Server Settings → Roles → Birthday Bot → Permissions, enable Manage Roles, and re-check. This permission is needed to give and remove the role. See Missing permissions.

The selected role belongs to an integration

Check: Look for Managed under Reason in the warning.

Fix: Choose a different, ordinary role under Birthday role and save. Discord does not let Birthday Bot hand out integration-managed roles. You can also create a birthday role from the picker.

The member does not qualify for the birthday role

Check: On Trusted roles, use Member check and inspect the birthday Role result. Check Blacklist too, and ask the member to confirm they have set their birthday for this server. Staff cannot tell a hidden birthday apart from one that has never been set.

Fix: Correct the relevant trusted-role rule or blacklist entry if the member should qualify. If their birthday is hidden, they choose whether to show it. See Choose who gets celebrated and Your privacy.

The birthday has not ended on the chosen clock

Check: On Birthdays, read Timezone, then check the relevant member or server time zone. It can already be tomorrow for you while it is still the member's birthday on that clock.

Fix: If the clock is wrong, follow A message was posted at the wrong time. If it is correct, allow the birthday to end there before expecting removal.

Using Discord instead

The test command refreshes role permissions and runs a real celebration, which can give roles and post messages. The settings command shows the configured birthday role.

The role-claim command covers zodiac roles and member-anniversary roles, not the birthday role.

/claim_role

Premium

Claim your zodiac or member anniversary role.

option

required · text

What type of role you would like to claim.

• Member Anniversary: Claim your missing member anniversary roles.
• Zodiac: Claim your missing zodiac role.