Skip to main content
Sync runs every two minutes, and immediately after any move. If it persists, /roster sync re-queues it.The database is right, so don’t fix it by editing the role in Discord — the next sync will just put it back.
Your role is resolved at login. Sign out and back in after any Discord role change.If it still won’t budge, check permissions — roster access in particular is division-scoped, so being a lead somewhere doesn’t grant it everywhere.
They haven’t submitted schedules. /admin/roster counts how many are missing.Availability is self-service — staff can’t fill it in on someone’s behalf, by design. Point people at /availability set.
The division requires a set number of evaluations before a decision. The error says how many you have and how many it needs./tryout config shows and changes the requirement.
They need a live membership in that division, and suspended players are refused outright.A lineup can’t name someone the roster doesn’t know — that’s what keeps sheets honest.
Appearances are counted from played lineups only. If sheets are being built but never closed out with /lineup set status:played, there’s nothing to count.
Discord can take up to an hour to roll out command changes. Nothing is broken; it just hasn’t propagated yet.
The dashboard header chip goes stale after three minutes without a heartbeat.The bot restarts itself. If it stays down, the website is unaffected — everything except role sync, announcement mirroring, and the slash commands keeps working normally.
A staff channel hasn’t been configured, so reminders fall back to the announcement channel. Set ROSTER_STAFF_CHANNEL_ID on the server and restart the bot.

​
Still stuck?

Check the audit log

/admin/audit shows every change with who, what, when, and from where. Most why did this happen? questions answer themselves there.