Testing and troubleshooting - Slack
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 and in the same format as a real alert. The test needs everything in place: a saved or just-entered token and a chosen channel. Missing either ends in a message about an incomplete configuration before DockRay even tries to reach Slack.
Common problems
The test fails even though the token looks right
The most common cause is a bot that was never invited to the target channel. The token authenticates the app, but Slack still checks whether that app is a member of the channel before letting it post anything there. Invite the bot with /invite @bot-name in the target channel and try again.
DockRay rejects the token on save
Validation requires the xoxb- prefix. A user token (xoxp-) or a signing token (xoxs-) looks similar but is not a bot token - Slack issues several different tokens for one app installation, and the DockRay form only accepts this one.
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, not on every repeat of it.
The platform channel doesn't work for a subscriber account
That is intentional, not a bug. The configuration with no account attached only serves Dock's internal projects - a subscriber never uses it, even if they happen to know the channel name.
A sudden error spike doesn't send a notification
The error-spike criterion is two conditions at once: a minimum number of events in the time window, and a sufficient multiple of that specific project's normal traffic. A quiet project that starts throwing the odd error may not clear the event-count threshold even with a real percentage jump. On top of that, this alert type is sent for the same project at most once every few hours - a repeat within that window is muted on purpose.
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.