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.

​
A thread as a log channel

A thread can be a log channel, and the troubleshooter checks it as one.
  • Quark’s webhook for a thread is in the channel the thread is in, and the thread’s permissions come from that channel. A missing permission or a full list of webhooks names that channel, and the fix is made there.
  • In a thread, Quark needs Send Messages in Threads where it would need Send Messages in a channel.
  • If the thread’s webhook is ever lost, Quark posts the logs in the thread itself, and for that its role needs Send Messages across the server. Without it, the troubleshooter says “Quark’s role is missing Send Messages, which a log thread needs”. Change this on Quark’s role in Server Settings, not on a channel.

​
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

​
When Quark tells you it can’t post logs

If Quark loses logs because it is missing a permission in a log channel, it tells the server. It also does this when the channel’s webhook is gone and Quark cannot make a new one. A lost webhook is usually replaced on the next log, so Quark only says something if logs are still failing a minute later. A deleted log channel gets no message. In a server of 1,000 members or more, Quark also checks a channel as soon as it is set as a log channel, and tells you straight away if it is missing something there.

​
Where the message goes

  • The DM only goes to someone still in the server with Manage Server or Administrator, or the owner. If nobody can be sent it, or their DMs are closed, it is posted in the server instead.
  • A post in the server goes to the system channel, or the first channel where Quark can post. It never goes to the channel that is broken.
  • Quark sends at most 2 messages for one problem, and at most one new problem per channel a day.
  • The message is in your server’s language.

​
What it says

The title is “Quark can’t send logs to #channel”. It names the missing permissions and says how many logs could not be posted since when. Where logs go through Quark’s webhook, Quark needs View Channel and Manage Webhooks. Where Quark posts them itself, it needs View Channel, Send Messages (Send Messages in Threads for a thread) and Embed Links. See in each log channel. In a DM, only the person it was sent to can press Check again or Ignore for this channel. In the server, anyone with Manage Server or Administrator can. Quark never changes your permissions itself. Give Quark the permissions in the channel’s settings, under Edit Channel → Permissions.

​
While the problem lasts

Logs that still arrive in your other log channels are posted under the name ⚠ Quark — some logs can’t be sent. They go back to the usual name once it is fixed. The problem closes when the next log is delivered to that channel, when Check again finds nothing missing, or when the channel stops being a log channel. The message then changes to Fixed and says when a log got through. If the channel is deleted, Check again changes it to Channel deleted. A problem with no lost log for 14 days closes on its own. The troubleshooter shows when Quark has already told the server about a problem: how many logs were lost, and when and where the message went. /troubleshoot also names the person who was sent the DM. The Quark Pro bot sends its own messages about its own log channels.

​
Another bot deleted Quark’s webhook

Some anti-nuke and security bots delete webhooks made by bots they do not trust. Quark posts logs through a webhook in each log channel, so when another bot deletes it:
  • Quark posts a notice in that channel naming the bot, at most once every six hours.
  • Quark makes a new webhook with the next log, and the other bot may delete that one too. Logs can be lost each time.
  • The troubleshooter lists it for a week.
To stop it, add Quark to that bot’s allow list. The notice in Discord and the troubleshooter give the steps for the bot that did it. Here they are for the bots with a guide of their own, and for any other bot. Quark’s ID is 704802632660943089. If you also use Quark Pro (ID 881671728491794442), do the same for that bot. Once Quark is on the list, nothing else needs doing: the next log makes a new webhook.

​
Wick

Wick watches webhooks in two ways: Anti-Nuke counts webhooks being made and deleted, and its heat system counts messages sent by webhooks as spam. Quark’s logs can trip either, so do both of these:
  1. Open Wick’s dashboard and pick your server. Sign in as the owner or an Extra Owner, because Wick’s Trusted Admins can’t change Anti-Nuke settings.
  2. Under Immunity & Permits, make Quark’s role a permit role and whitelist it from Antinuke limitations. Save.
  3. So Wick stops counting Quark’s logs as webhook spam, run w!whitelist #your-log-channel in Discord and choose Spamming. Use your own prefix if you changed w!.
See Wick’s setup guide for more on its whitelist and Anti-Nuke.

​
bleed

  1. As the server owner or an antinuke admin, run ,antinuke whitelist 704802632660943089, or ,antinuke whitelist 881671728491794442 for Quark Pro. Use your own prefix if you changed ,.
  2. Run ,antinuke list and check Quark is on the whitelist.
See bleed’s antinuke docs for more.

​
Any other bot

  1. Open the bot’s dashboard or settings and find its anti-nuke or security section.
  2. Add Quark to its allow list. It may be called the whitelist, trusted list or exempt list. If it asks what to allow, allow managing webhooks.
  3. If the bot only allows roles, allow Quark’s role.

​
Quark was removed as soon as it joined

Some security and anti-raid bots remove any bot that joins until they are told to allow it. If Quark is removed seconds after you add it, that is almost always why. The setup page and the dashboard say so, list the bots known to do this, and show the steps for the one you pick. Quark can’t tell which bot it was: once removed, it can’t see your server. Server Settings → Audit Log shows which bot removed it. Quark’s ID is 704802632660943089, and Quark Pro’s is 881671728491794442.

​
Wick’s Join Gate

Wick’s Join Gate has a Bot Addition Filter that removes bots added by anyone it doesn’t trust.
  1. Have the server owner, an Extra Owner, a Trusted Admin, or someone whose highest role is above Wick’s invite Quark. Wick lets them add bots.
  2. Or switch the filter off while you add Quark: run w!jg 4a ?off, invite Quark, then run w!jg 4a ?on. Use your own prefix if you changed w!.
  3. Still removed? Wick’s Unverified Bots filter may be on as well: do the same with w!jg 6a ?off and w!jg 6a ?on.
See the Join Gate section of Wick’s setup guide.

​
Security’s Bot Add trigger

Security’s Anti-Nuke treats adding a bot as an instant trigger: it kicks the new bot and punishes whoever added it (a kick, unless your server changed it). Check that person is still in the server and has their roles.
  1. Have the server owner, or someone with a role above Security’s, invite Quark. Security leaves them alone.
  2. Or whitelist the person who will add Quark: run /whitelist add_user, pick them, and choose the bot add category (or Global).
  3. Or switch the trigger off while you add Quark: /disable and pick Bot Add, invite Quark, then /enable and pick Bot Add.
See Security’s docs on switching triggers.

​
bleed’s antinuke

bleed’s antinuke botadd module removes bots that aren’t on its whitelist.
  1. As the server owner (or an antinuke admin), run ,antinuke whitelist 704802632660943089, then invite Quark. Use your own prefix if you changed ,.
  2. Whitelisting lets Quark past all of bleed’s antinuke. To avoid that, run ,antinuke botadd off, invite Quark, then ,antinuke botadd on instead.
See bleed’s antinuke docs.

​
Another bot

  1. Open Server Settings → Audit Log: it says which bot removed Quark.
  2. In that bot’s settings, find what removes new bots. It is often called bot add, join gate or anti-bot.
  3. Have the server owner invite Quark, or add Quark to that bot’s allow list, then invite Quark again.

​
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.A log format leaves Edit Reason off a modlog it has rearranged: a compact or Advanced one, one laid out with Components or drawn as a picture, or one with the footer, the time or one of its first three fields hidden. The same goes for Show Edits on an edited message. On an older modlog whose format has since changed to Components or a picture, Edit Reason replies that its reason can’t be edited in that layout. Lock and History still work.
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. Pro is put on the server when checkout completes, so add the Pro bot from the page you land on afterwards. On a plan bought before Pro was locked to a server, apply it 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 the Billing tab of your account to see which servers have Pro.

​
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.