Synchronisation with the bot

The website and the bot don't talk to each other directly: they share the same database and the same Redis server (an in-memory cache that also works as a messaging system), through a common library, the config service.

• The database holds your server's whole configuration. What you save on the website, the bot reads from the same place.
• Redis keeps a fast copy (a cache) of the most-read settings, and carries small messages between the website and the bot.
• The website also reads Discord directly: your server list, the channels, roles and emojis shown in the pickers. It only creates a few things itself (for example a channel when you click a create button); everything else (messages, panels, sanctions, commands) is done by the bot.

1. Save: the website stores your configuration in the database and clears the matching cache.
2. History: it adds a row to Configuration Logs, with your name and the before / after.
3. Message to the bot: for most modules, it publishes a configUpdated message on Redis with the configuration type and the list of changes.
4. Bot reaction: the bot clears its own caches for the server, reads the configuration again, does what the module requires (register commands, post a panel, apply raid mode…) and posts a "Configuration Update" message in the log channel, with your name and Web Dashboard as the source.
5. Live update: the website also publishes an event specific to the page; every tab open on that page updates (see below).

Applied immediately, with a message to the bot

Read straight from the database

For these pages, the website clears the shared cache when saving: the bot reads the new version the next time it needs it.

Checked on a schedule

Sent to the bot as an action

While a dashboard page is open, the website keeps a connection open with the server (Server-Sent Events) and receives these events:

• Settings changed with /config: they're saved in the same database, so they show on the website on the next page load (no live update). They don't appear in the website's Configuration Logs, only in General Server Logs on Discord.
• Channels, roles, emojis, bot permissions: the website keeps a copy of the server's Discord data for 30 minutes. To see a channel or role you just created right away, click Sync Discord Data at the top of the page (at most once a minute; otherwise a "Cooldown active" message appears).
• Member and bot lists in the pickers: kept for 30 minutes; only the first 100 members are offered (you can always paste a Discord ID).
• Audit logs and Configuration Logs: data kept for 30 seconds, pages refreshed every 15 seconds.

Some actions ask the bot to do something right now and wait for its answer:

1. Check that the bot is online on your server: if the bot restarts at the moment you save, the setting is in the database and will be read (right away or within an hour at most, depending on the module), but one-off actions (log message, command registration, panel posting) aren't replayed. Save again.
2. Look at Configuration Logs: if your change isn't there, it wasn't saved.
3. Check the bot's permissions on Discord: a setting can be saved but impossible to apply (for example without Manage Roles). See Permissions and roles.
4. A channel or role missing from a picker? Click Sync Discord Data.
5. Social networks and RSS: wait for the next round or use Check & send.
6. New commands not showing: reload Discord (Ctrl + R).

More leads in Website troubleshooting.

• Logs: Configuration Logs and audit log.
• Managing permissions
• Logs (module): the bot's log messages.
• Redis and database: the technical details (team only).