Skip to main content

​
Run the troubleshooter first

Quark has a built-in troubleshooter. It checks your configuration, Quark’s permissions in each log channel, and the delivery path, then lists what it found, most serious first.
Run /troubleshoot in your server. You need Manage Channels and Manage Server.The reply is only visible to you. Set share to true to post it in the channel instead, for example when asking for help. A shared report shows channel names, ignore list entries and missing permissions to everyone who can see the channel, so share it in a staff channel.
The report has one of three headlines: Where a problem can be fixed without a decision from you, the troubleshooter offers a button: Fix this on the dashboard, or Register webhook, Remove ignore rule or Stop ignoring bots in Discord. Run the troubleshooter again afterwards to confirm.

​
Send a test log

Both versions of the troubleshooter have a Send a test log button. It sends one real log, visible in the channel your Quark Events logs go to, through the full delivery path, and tells you whether it arrived or where it stopped. You can use it once a minute per server.

​
Problems that stop logs

​
Problems that affect some logs

​
Settings that explain missing logs

These are choices your server has made. The troubleshooter lists them because they are the usual answer to “why did this one not appear”.

​
Other problems

Quark can only show the content of a message it saw being sent and still has stored. On the free plan and Pro Lite that is 12 hours. On Quark Pro it is 30 days. Messages sent before Quark joined, or while it could not see the channel, cannot be recovered.See message age.
Open the entry in the log viewer. If it is marked Held back by rule, an automation rule with Don’t send this log held it back. Switch that rule off, or change its conditions, on the Automations page. Otherwise the entry’s Delivery status says why the log did not reach Discord.
Look at the rule’s row on the Automations page, and at the latest Rule Action log about it in your Quark Events channel. They say what is missing.If it is the person who last changed the rule, they have left the server or lost the Discord permission the rule uses. Someone who holds that permission has to edit the rule, or switch it off and on. See if a rule stops acting.If the row says the rule ran more often than a rule is allowed to in an hour, it has reached an hourly limit and starts again in the next hour.
On a server with an automation rule that moderates, a change that lets more be logged needs the Discord permissions those rules use. Removing an ignore rule and switching a log type on are two such changes. People who manage the server need those permissions too.Ask someone who has them to make the change. See changes that let more logs reach a rule.
On a busy channel, Quark can post several logs in one message. A modlog posted that way has no Edit Reason or Lock button, and its reason cannot be edited. Whether a channel is busy is counted for each channel, so giving Modlogs a channel of their own makes this less likely.A modlog also has no Edit Reason button when Modlog reasons was set to Never editable when it was posted. See modlog reasons.
The reply says why. An image has to be a PNG, JPEG, GIF or WebP of up to 6 MB, and a modlog holds up to 4. A locked modlog, or one that shares its message with other logs, cannot be given images.If the reply says Quark needs Attach Files, give Quark that permission in the modlog channel. See modlog images.
Both only work on a log posted by the bot whose command you chose. If Quark and the Quark Pro bot are both in your server, each has its own Get IDs and Report log issue in the Apps menu. Choose the one from the bot that posted the log.
If Discord reports a log channel as unknown five times in a row, Quark clears that channel from your configuration. This happens when the channel, or Quark’s webhook in it, is deleted. Choose the channel again.
Most commands are hidden from members without the required permission. Check Server Settings → Integrations → Quark to see who can use each command. See the command list for the defaults.
The Pro bot leaves any server that does not have Quark Pro when it joins. Apply your subscription to the server first, then add the Pro bot. See getting started with a subscription.
You need Administrator, Manage Server, Manage Channels or Manage Webhooks in the server, or someone with one of those has to give you access.
When a plan ends, Quark keeps your settings but stops applying the paid ones: custom colours, formats, per-log channels and logging of bot actions. They apply again when the server has a plan. Check your inventory to see which servers your plan is applied to.

​
Still stuck?

Ask in the support server. Post a shared /troubleshoot report if you can. If support asks for a debug report, run /debug. It sends Quark’s developers a report with your server ID, Quark’s permissions, your plan and Quark’s configuration for your server. Only run it when support asks. Check status.quark.bot to see whether Quark is having problems of its own.