Summary:

When creating custom Rovo Agents, customers might observe different behaviors when interacting with them directly in Rovo Chat compared to Slack.

For custom Rovo Agents with over 10 scenarios, unexpected issues may occur: Rovo adds the :eyes: emoji to the thread but doesn't respond. This problem could stem from having a number of scenarios exceeding the acceptable threshold. Custom Rovo Agents with 10+ scenarios may exhibit unexpected behavior: Rovo adds the :eyes: emoji to the thread but never delivers a response. This may be due to a higher-than-threshold number of scenarios.

 

Request:

Add some sort of feedback back to the Slack thread if the Rovo fails to process the request or exceeds any sort of timeout.
 

Workaround:

Break down the scenarios into multiple Rovo Agents, or merge scenarios, ensuring the final number stays under 10.