Custom agent able to read Slack thread

[Vivien RUIZ]

Hello,

I created a custom agent, and added it to a Slack channel with a keyword trigger.

When triggering the agent, it is unable to read messages posted previously in the thread.
The agent constantly answer "Could you please provide the link or channel and timestamp of the Slack thread you want summarized? This will help me retrieve the conversation"

I have added the "Read messages in Slack" skill and granted the Slack custom knowledge.

Is this a know limitation of custom agent ? I do observe that the general Rovo agent has no trouble providing a summary of what was discussed

[Dr Valeri Colon _Connect Centric_ · Accepted solution]

Welcome to the community @Vivien RUIZ Custom agents can’t read full Slack thread history. The built-in Rovo Slack bot uses Slack’s native thread context, but custom agents don’t receive that message history even if you enable the “Read messages in Slack” skill. They only get the single triggering message unless you explicitly pass thread data to the agent. This is a current limitation of custom agents in Slack.

[Jorge Cammarota]

Good evening, I have had some similar problems before. Check if the widget is correctly configured in Jira Go to the Jira Service Management of the service project:

Project settings → Channels → Widget.

Check:

The channel is enabled.

The domain where the widget is running is included (allowed domains / trusted domains, depending on the version).

Copy the updated Embed snippet (script) again.

If anything is different, update the code in Scroll Sites and test again.

Check CORS/domain and browser blocks The text “Something went wrong” with technicalReason:null is very typical of:

Domain not allowed in the widget; or

Network error blocked by the browser (CORS, mixed HTTPS, etc.).

On the site where the widget is embedded:

Open the site in an incognito tab.

Open the browser DevTools → Network and Console tab.

Reload the page and check for:

Requests to *.atlassian.net or jsmstatic.com failing (status 4xx/5xx).

CORS, mixed content, or script blocking messages in the Console.

If there is a 403/404 error for the widget or JSM URL, it is almost always an unauthorized domain issue.

If this doesn't solve it, show us the error that occurred so we can help you together, my friend.