Testing and troubleshooting - Discord
The test message
A Send test button sits next to every event type. It posts a sample message with the project name, the event type and the detection time - down the same path as a real alert. It needs a saved or just-entered bot token and a valid channel ID. Missing either ends in a message about an incomplete configuration before DockRay even tries to reach Discord.
Common problems
The test fails with a permission error
The most common cause is a missing Send Messages or View Channel permission on the target channel - the bot's role may have server-level permissions, but that specific channel can have narrower ones overriding it. Check the channel's own permission settings, not just the bot's role.
The message arrives, but without formatting or a link
That is a missing Embed Links permission. Without it, Discord still lets plain text through, but drops the content DockRay uses to send a title, a colour and a button linking to the panel.
DockRay rejects the channel ID on save
The field only accepts a string of 17 to 20 digits. A pasted channel link or its name will not pass validation - copy the ID using Discord's developer mode (User Settings → Advanced → Developer Mode), then right-click the channel → Copy Channel ID.
The configuration is saved, but notifications still don't arrive
Check the routing for that specific event type - it may be set to 'don't send', or the project may have explicitly overridden the account's inheritance. It is also worth checking whether the event actually happened: issue only fires on the first occurrence of a new error.
A sudden error spike doesn't send a notification
The error-spike criterion needs a minimum number of events in the time window and a sufficient multiple of that project's normal traffic at the same time, and this alert type is sent for the same project at most once every few hours.
Still not working
Work through the troubleshooting checklist, and if that does not help, write to us. Include the project name, the integration version and roughly when you ran the test: it shortens the way to an answer.