My AI agent is unable to handle more than 10 agents conversation at a time

[banditapani]

Hi Experts, 

I have an AI agent, and it gives me correct result when I have 1 active conversation in VA. When I initiate more than 10 conversations or when 10 people are using the same agent for their answers. Even if different users are initiating conversation, this agent is getting stuck after a max limit of around 10 active conversations. 

Did anyone face this issue? because if an AI agent is created, ideally entire organization will use it. Is there something am missing to setup?

[Dr Atul G- LNG]

Hi @banditapani 

https://www.servicenow.com/community/now-assist-articles/ai-agents-faq-and-troubleshooting/ta-p/3200...

 @Victor Chen 

[banditapani]

ADDITIONAL INFORMATION : 

Issue

If we call an agent with below code

{

            triggerConfigId: "",

            targetRecordId: userInput,

            agentId: agentId,

            conversationUser: currentUserId,

            objective: userInput

        }

 var agentResponse = new sn_aia.AiAgentRuntimeUtil().startAiAgentConversation(payload);

Then if we run this code >4-5 times in a queue, i.e. trigger agent around 5 times, 5 ai agent executions start and 5 sys_cs_conversations get created but when we trigger for 6th time, no execution or conversation is created

This is an issue as we may be calling the agent with static user sys id and agent can be used by multiple users at same time causing multiple executions

[rpriyadarshy]

@banditapani  Have a look on this Since Conversation is Triggering from VA.

ServiceNow Virtual Agent chat messages are processed using a dedicated worker thread pool, specifically "glide.cs.worker.num_workers", which by default has a pool size of 2. This means your instance's configuration of 2 dedicated server threads for VA chat aligns with the standard setup. 

CAUTION: If you need to adjust this setting or require further customization, you can do so by modifying the "glide.cs.worker.num_workers" property in your instance.

Please Consult with Support also before Tweaking this Property.

Regards

RP