> ## Documentation Index > Fetch the complete documentation index at: https://docs.neo.projectdiscovery.io/llms.txt > Use this file to discover all available pages before exploring further. # Troubleshooting > Diagnose Slack install states, reconnect problems, channel issues, and other common Neo-in-Slack edge cases. This page helps you diagnose the most common Slack integration problems in Neo. ## Installation States Neo tracks Slack workspace lifecycle states internally. These states explain why the app may appear connected, disconnected, or partially set up. ### `active` Meaning: * the workspace is connected to Neo * the install is tied to a Neo team — either auto-created on install for solo users, or an existing team for team admins * the connection is ready for normal use If something still does not work in this state, check user access, channel behavior, or reinstall requirements after new permissions were added. ### `pending_unclaimed` Meaning: * Slack installation completed * Neo has not yet tied the workspace to a Neo team through the claim/setup flow What to do: * complete setup from Neo as a Neo team admin ### `revoked_external` Meaning: * Slack access was revoked or invalidated outside Neo * Neo can no longer operate until the workspace is reauthorized What to do: * reconnect or reinstall the workspace from the Slack integration flow * make sure the latest permissions are approved ### `disconnected_by_user` Meaning: * a Neo team admin intentionally disconnected the workspace from Neo What to do: * reconnect it from Neo settings * do not assume a plain Slack reinstall will fully restore it ## Only Admins Can Manage An Existing Team's Workspace Symptoms: * reconnect/disconnect buttons are not usable * the connect button shows "only team admins can connect Slack" Cause: * you are a non-admin member of an existing Neo team; only that team's admins can manage the workspace connection What to do: * ask your Neo team admin to complete the flow inside Neo This restriction does **not** apply to Neo users who don't yet belong to a team. Solo users can install Slack themselves — Neo auto-creates a team for them on install. ## Workspace Already Connected To Another Neo Team Symptoms: * Neo reports that the Slack workspace is already connected elsewhere Cause: * the workspace already belongs to another Neo team in Neo's ownership model What to do: * resolve the ownership from the existing Neo team before trying to reuse the workspace ## Neo Is Disabled In This Channel Symptoms: * Neo refuses to act in a specific channel * Slack returns a message directing you to admin settings or DMs Cause: * the channel is disabled for Neo use in the workspace configuration What to do: * ask a Neo team admin to enable the channel in Neo settings * or use a DM instead ## A Thread Is Already Running Symptoms: * Neo indicates it is already working on an earlier request in the same thread Cause: * Neo protects the thread from overlapping active runs What to do: * wait for the current run to complete * or abort the active run with a supported reaction if it is no longer needed Supported abort reactions: ```text theme={"system"} 🛑 ❌ ✋ 🚫 ``` ## Reaction-Based Abort Does Not Work Symptoms: * adding a supported reaction does nothing Common causes: * the task is no longer running * the workspace installed Neo before reaction-based abort shipped * the workspace has not been reinstalled or reconnected after new permissions were added What to do: * confirm the task is still active * reconnect or reinstall the Slack app * make sure the workspace approved the updated permissions and event subscriptions ## User Can See Neo But Cannot Use It Symptoms: * the workspace is connected, but a specific user cannot get Neo to run tasks Cause: * the user may not map cleanly into Neo * the user may not have the required Neo access * Neo AI access may not be enabled for that user What to do: * verify the user belongs to the right Neo team * verify the user has the required Neo access * retry from a DM if channel configuration is a factor ## App Was Reinstalled In Slack But Still Does Not Work Symptoms: * Slack install appears fresh, but Neo still behaves as disconnected or unavailable Cause: * a Slack-side reinstall only auto-restores when the previous state was `revoked_external`. If a Neo team admin previously disconnected the workspace from inside Neo (`disconnected_by_user`), Slack-side reinstall does not bring it back to `active` What to do: * check the workspace state under Neo Settings → Applications. If it shows `disconnected_by_user`, a Neo team admin needs to reconnect from Neo. If it shows `revoked_external` or `active` after the reinstall, the integration should work — try a fresh `@Neo` mention or DM to confirm ## Still Need Help? Use the public support and trust resources here: * [Slack Privacy & Support](/integrations/slack-privacy-and-support) * [ProjectDiscovery Support](https://projectdiscovery.io/support) * [ProjectDiscovery Contact](https://projectdiscovery.io/contact)