Rovo Agent stops responding in Slack after model migration — eyes reaction appears but no thread rep

[Richard Chen]

Our Rovo agent "SORT Concierge" has stopped responding in Slack threads after a keyword trigger. The Slack app recognizes the trigger (adds an eyes reaction) but the agent never generates a thread reply.

Site: sendbird.atlassian.net

Agent: SORT Concierge

Slack Channel: #sort-request-test (C0AJZVDC6KB)

Keyword Trigger: !SORT

Symptoms:

1. When a user posts a message starting with !SORT, the Rovo Slack app adds an eyes reaction but no thread reply is generated.

2. The /Rovo add command in Slack shows "We had some trouble connecting. Try again?" error.

3. The agent works perfectly in the Rovo Studio Test panel. The issue is isolated to the Slack integration.

Timeline:

- Working normally through April 28, 2026

- Intermittent failures on May 1, 2026 ("Something went wrong" errors)

- Complete failure on May 4, 2026 (zero thread replies, only eyes reactions)

Troubleshooting performed:

1. Verified agent works in Rovo Studio Test panel

2. Verified Slack surface is configured in Rovo Studio

3. Toggled "Swap to new model" from OFF to ON

4. Attempted /Rovo add to re-register agent (got connectivity error)

5. Sent test messages after each change (still no response)

Suspected cause: The issue may be related to the Rovo backend model migration (announced for April 14, 2026). The /Rovo add dialog showing a connection error suggests the Slack-to-Rovo agent pipeline has a backend connectivity issue.