Slack events are not delivered

Slash Social relies on Slack to deliver app events such as App Home opens, direct messages to the bot, link shares, and file uploads. When those events stop arriving, workflows feel frozen even though the app still appears installed.

Workspace admins should run the checks below. Creators can confirm symptoms; reinstall and permission fixes need an admin.

Symptoms

• App Home never refreshes after you complete an action elsewhere in Slack.
• Direct messages to the Slash Social bot go unanswered.
• Link previews or intake cards stop updating when you share URLs.
• Message shortcuts that used to open Create no longer open a modal.
• /social works in a channel, but App Home and DM-based flows stay silent.

Checks

Narrow the failure before you reinstall:

1. Ask whether every user sees the issue or only some channels or DMs.
2. Confirm Slash Social still appears in the workspace app list and was not removed or restricted.
3. Test /social in a channel. If it responds, slash commands work but event delivery may still be broken for App Home or DMs.
4. Open Slash Social App Home from the Slack app list. Note whether sections load or stay on an old snapshot.
5. For bot intake, open Messages with Slash Social and send a test (not a channel @mention).
6. Note when the problem started, especially after a Slash Social release or workspace permission change.

Likely causes:

• The workspace install is outdated after Slash Social added new Slack permissions or event subscriptions.
• The app was removed or restricted by a workspace admin.
• Users interact in a channel thread instead of a direct message with the Slash Social app where the workflow requires DM.
• Slack client caching shows stale App Home until you reopen the app.

Fixes

1. Refresh the install. Ask a workspace owner to reinstall from https://go.slashsocial.app/slack/install. Review and accept any new permission prompts.
2. Verify slash commands. Confirm /social loads in a channel after the refresh.
3. Reload App Home. Open Slash Social App Home from the Slack app list and confirm sections load.
4. Retest DM intake. Open Messages with Slash Social and send the test again (not a channel @mention).
5. Clear stale UI. Close and reopen App Home or reload the Slack client if the home tab looks unchanged after a successful action elsewhere.
6. Retest message capture. Use a message shortcut or paste a link through /social to confirm Create modals open. See Save Slack messages as social content.

For first-time setup steps, see Install Slash Social in Slack. For DM-only intake issues, see DM intake is not working.

Confirm the fix

App Home updates after you complete an action. /social responds in channel. DM or link tests produce the expected intake card or modal. Message shortcuts open follow-up Create surfaces again.

Prevent it next time

• Reinstall after Slash Social announces new Slack permissions or event subscriptions.
• Train the team to use Messages with Slash Social for bot intake, not channel @mentions.
• After large Slack client updates, reopen App Home once before you report a delivery issue.

Contact support

Contact support when a fresh install succeeds but App Home and DM tests still produce no response for every user in the workspace.

Send the workspace ID, approximate start time, which workflows fail (App Home, DM, link share, message shortcut), and whether /social still opens in channel. If only DM intake fails, include results from DM intake is not working checks first.