My Slack card didn't update, or a button did nothing
The important thing first: the card is not the record. Scout's item in the app is. A card that failed to update is not proof your action failed, and a card that updated is not the only proof it worked. Check the item in Scout before doing anything twice.
Check these in order
- Is your Slack account linked to your Scout seat? Scout only accepts actions from a confirmed link. Confirm the proposal Scout sent you, or link yourself with the /scout link command. See Linking your Slack account to Scout.
- What is your role? A Viewer cannot claim, handle, or dismiss anything from anywhere, Slack included. The same authorization rules apply on every surface.
- Were you dismissing? Dismiss requires a note. Scout opens a small window to collect it, and an empty note is rejected. If that window was closed, the dismissal never happened.
- Is the card old? Cards go stale when the item changed elsewhere — someone else claimed it, or Scout settled it on evidence. Scout tries to replace a stale card a limited number of times and then stops rather than retrying forever. Open the item in Scout with Open in Scout to see where it actually stands.
- Is the workspace's Slack connection healthy? If the installation was paused, retired, or reconnected, older cards are not carried over to the new connection. An Owner or Admin can check it under Connections.
Where to look next
Settings → Workspace → Notifications carries your own Slack delivery diagnostics — your last seven days, up to twenty-five records each of deliveries, cards, and accepted actions, for you and nobody else. An empty list does not prove nothing was sent. See Slack delivery diagnostics.
There is deliberately no force-resend and no reset. If the item in Scout does not reflect what you did, act in the app and tell support, quoting the timestamp and the reason shown in the diagnostics panel.