Is it down?
Checking whether an issue is with your server or with TalciGrade.
The status page tells you whether TalciGrade is working. It reports each of the bot's clusters, the website and everything behind them separately.
Shards and clusters
Discord requires large bots to be split up. A shard is one connection to Discord that handles a share of the servers the bot is in, and a cluster is a group of shards running together.
Your server is handled by one shard in a cluster, always the same one. A shard carries many servers, so a shard with a problem affects every server on it, not only yours. What it does not affect is the servers on the other shards, which is why the status page lists each cluster separately rather than reporting the bot as one thing: "one cluster is down" is a real and common state, and it is not the same as TalciGrade being down.
You can find which shard and cluster your server is on by running /ping, or from the sidebar on the Dashboard.
What the states mean
| State | Meaning |
|---|---|
| Operational | Working normally |
| Degraded | Working, but with a known problem |
| Maintenance | Planned work is in progress, or the component was added to the page in the last 15 minutes and is not responding yet |
| Offline | Not responding |
Planned work shows as Maintenance rather than Offline, because it was scheduled in advance. If a component is still unavailable when the window ends, it changes to Offline automatically.
A component that has just been added to the status page shows as Maintenance rather than Offline for its first 15 minutes if it is not responding. If it is still not responding after that, it changes to Offline. While this is the only reason anything shows as Maintenance, the banner at the top of the page reads "Some systems are starting up".
Time spent in Maintenance does not count against a component's uptime.
Updates
An incident is published on the status page with updates as it is worked on, and the time it was resolved.
The page refreshes itself. No reload is needed.
Before reporting a problem
- Check the status page, in case we already know
- Check TalciGrade has permission to do what you expected
- Check the TalciGrade role is above the roles it needs to manage
- Check the module is turned on and you have set a channel for it