| Symptom | Check |
|---|---|
| Connecting your account fails with “The MCP server refused to start a session (HTTP 400)” | Check that Agents › MCP is enabled in the same Slack app whose client ID is saved in OpenWork. This is separate from enabling the assistant bot. See Slack MCP connection troubleshooting. |
| Setup is unavailable | Private-alpha capability, runtime access, and Individual accounts mode. See step 1. |
| Bot missing from mention autocomplete | Bot installation completed and the bot is invited into that channel with /invite @openwork. |
| Slack events URL unverified | Public HTTPS URL, correct connector ID, saved signing secret, and Slack’s Retry then Save Changes. |
/openwork gives a connect link | Complete your own Slack OAuth flow. Connections made before the assistant was installed link automatically on your first message; reconnect only if it still asks. See Connect your account. |
| Bot starts but never finishes | Check failed/active counts and runtime availability; do not treat an acknowledgement as success. |
| DMs work but channel mentions do not | Channel allowlist, channel invitation, connector grants, and assistant enablement. |
OpenWork in Slack (private alpha)
Troubleshoot OpenWork in Slack
Fix @openwork missing from Slack autocomplete, an unverified events URL, connect links that repeat, or a bot that starts but never answers.
To pause the rollout, turn off Enable @openwork in Slack in the connector. Disabling new requests cannot recall external actions that have already run.
Was this page helpful?