Diagnose Agentforce Slack Connectivity

1. Starts from the symptom the user reports. Examples are an agent missing from Slack Admin, rebuilt agents that are active but missing from the Slack agent picker, or an agent that needs fixing before its Slack routing is checked.
2. Reads the agent configuration and checks the Slack routing.
3. Traces the root cause, sometimes by comparing a working org with the failing one. In one case the failing org lacked a Slack authentication connected app because an org permission was not enabled. In another it found that agents need both an agent access entry in a permission set and a Slack connection directive in Agent Script.
4. Where the agent side needs work, it fixes and republishes the agent. It removed an empty access block that blocked a commit and published a new version, and it republished agents through authoring bundles and checked their bot version status.
5. Writes up the diagnosis as a comparison artifact and a remediation plan.

Once the connection works, the next step is usually Deploy Agentforce Agents to Slack.