Slack delivery diagnostics
When a Slack update did not arrive, or arrived twice, or a card looks out of date, Scout can show you its own record of what happened to your Slack messages. The panel is read-only: checking it does not send a message, retry a delivery or change any setting.
Opening it
- Open Settings → Workspace → Notifications.
- Find Slack delivery diagnostics. The line underneath states what it is: read-only support checks.
- Choose Refresh diagnostics. The button reads Checking diagnostics… while it loads.
The report is built on demand and not stored. If it cannot be verified, Scout says so and shows you nothing rather than an old report: "Slack diagnostics could not be verified. Reload your workspace or try again. No previous report is shown."
What it covers, and what it does not
Everything in the panel is yours: your delivery metadata, for items you can currently see. Administrators cannot inspect another person's private deliveries here — they see the workspace's Slack installation health instead.
The window is the last 7 days, and each list shows the latest 25 records in that window. That means:
- An empty list does not prove no message was sent. Older records, deleted records and records for items you can no longer see are excluded.
- This is not the full ledger. For older history, open the item in Scout and read its Action history.
- It is not a message search, not a proof of completeness, and not a resend or reset tool. No such tool exists, on purpose.
Current eligibility
The first section answers "could a Slack message reach me at all right now?" — whether Slack is configured for the workspace, whether delivery is switched on, the state of your account link, whether a fresh email match is waiting for your review, whether your Assigned to me and Items I follow Slack boxes are ticked, and whether quiet hours are configured.
Read it as a statement about now, not about the past. These checks are not proof that a message was or was not sent yesterday.
The three histories
| Section | What it records |
|---|---|
| Original deliveries | Each update Scout tried to send you: its reference, its status, when it was updated, when it was due to go, how many attempts were made, how many were accepted, and a plain-language reason. |
| Card replacement attempts | Each attempt to replace a sent card with a receipt: whether the original delivery was accepted, how many replacement attempts were made, the latest outcome, and when the metadata will be discarded. |
| Your canonical Slack action receipts | Each action you took from a Slack card, whether it changed anything, and when. |
These three are separate records on purpose. "Accepted" means Slack acknowledged the request, not that a person saw the message. A successful card replacement is not proof that your action was recorded, and a missing replacement is not proof that it failed.
The four words to look for
Missing
Nothing arrived. Check, in order: that your Slack account is confirmed; that the Slack boxes are ticked for Assigned to me and Items I follow; and your quiet-hours setting. If those are all correct, an Owner or Admin should check the Slack connection under Connections. Never link somebody else's account to test it.
Late
The message is queued but has not gone. Use the recorded reason and the time it became available. Work sitting more than 15 minutes past its available time needs attention. Do not try to resend it by hand — there is no way to, and duplicating a send is worse than a delay.
Duplicate
You think you got the same update twice. Compare the delivery references and the accepted-attempt counts. A retry is not a second delivery, and two different references may genuinely be two different updates to the same item. Remember too that the original card, its replacement receipt and your action receipt are three records, not three messages.
Stale
A card is showing something you know is out of date. Open the item in Scout and read its current state and receipt — that is the authority. A replacement attempt recorded as prepared or unknown is not a confirmed success, and it is not a reason to clear anything or force a resend.
Getting it fixed
- You can unlink or re-confirm your own Slack account, and change your own preferences.
- An Owner or Admin handles the workspace's Slack connection — pause, resume, reconnect, revoke — and any question of access or configuration. Reconnecting does not restore old consent and does not replay messages whose outcome was uncertain.
- Scout support handles the rest: unknown delivery outcomes, genuinely duplicated accepted attempts, persistent retries and stale-card incidents.
When you contact support, send only the timestamp, the fixed reason and the opaque reference from the panel. Never send message content, tokens, link codes or anything from your Slack channels — Scout does not need them and cannot read them.
Good to know
- The panel keeps nothing between visits. Close the page and the report is gone.
- At most five recent installations are listed in the administrator section, and a retained health record is not proof that a token is currently valid.
- If the whole workspace has no Slack connection, the diagnostics will tell you that before you go looking for a missing message.