How to fix: There are no agents available at the moment. Please try again later.

[Pooja Deshmane]

Hi all,

I have created AI agent which summarizes the custom table records and i have also enabled  "Engage via Otto chat assistants" and selected my custom portal record. This is working fine in dev but able to see "There are no agents available at the moment. Please try again later." when moved to QA.

Plugins are already repaired.

conversation interface already configured for assistant.

Please suggest what might be causing this issue.

[Dan_Junqueira]

Hi @Pooja Deshmane 

Since it's working fine in DEV but not in QA, I would first check whether all the AI Agent configurations and dependencies were properly moved between instances.

A few things I would look at:

1. Make sure the AI Agent and its Agentic Workflow are both active in QA.

2. Double-check the Engage via Otto chat assistants configuration. Sometimes the agent is migrated, but the association with the assistant or channel needs to be reviewed.

3. Verify that the user testing in QA has the necessary roles and permissions, especially for the custom table.

4. Try running the Agentic Workflow directly in QA, without going through Otto. This should help identify whether the issue is with the agent itself or the chat integration.

I also noticed the message "Sorry, there was a problem on my side trying to complete this request" before the "There are no agents available" error. It might be worth checking the AI Agent execution logs to see whether the request is actually reaching the agent.

My guess is that something related to the agent's availability or configuration didn't carry over correctly to QA, especially since everything works in DEV.

One question: Did you migrate the AI Agent using an Update Set or through the Application Repository? That could help narrow down the issue.

Hope this helps! If it resolves your issue, please consider marking this reply as Accepted Solution and Helpful so others facing the same problem can benefit from it too.

Thanks!
Dan,

[Pooja Deshmane]

Hi Dan,

I had migrated the AI Agent using update set. Checked below points:

1. The AI Agent and its Agentic Workflow are both active in QA.

2. assistants configurations are also same as dev, channel is also correct.

3. currently checking with my profile, i have admin role.
4. This is working fine from native UI and No agents available issue occurring when tested from portal. Also have seen one more thing that, if i click on button "Pace Summary Agent", and then providing the number it is showing me expected output. but if I directly send a message "pace summary for <pace number>" without clicking on button, it is showing me No agents available message.
5. One more thing i have checked, when tested assistant from conversation interface, still it was showing same no agents available message.

[Dan_Junqueira · Accepted solution]

Hi @Pooja Deshmane ,

Thanks for sharing the additional details. This actually helps narrow down the issue quite a bit.

Since the agent works when you click the Pace Summary Agent button and provide the record number, but fails when you type the request directly, I don't think the problem is with the agent execution itself.

It looks more like an agent discovery or orchestration issue in QA.

I would suggest checking a few things:

1. Agent proficiency: Compare the agent's proficiency description between DEV and QA. This is particularly important because the orchestrator uses this information to determine which agent should handle a user's request. Make sure the description clearly explains what the agent does and when it should be invoked.

2. AI Search: Verify that AI Search is enabled and configured correctly in QA. Agent discovery can depend on this functionality.

3. Agent instructions: Check whether the agent instructions clearly describe the requests it should handle. For example, the agent should be able to recognize something like "Pace summary for PACE12345" and associate it with the appropriate workflow.

4. Orchestrator logs: Try the same natural-language request in both DEV and QA, then compare the execution logs. This should help determine whether the orchestrator is failing to identify the agent or whether something else is preventing execution.

5. Deployment dependencies: Since you migrated using an Update Set, I would also double-check whether all the related agent metadata and configuration records were included. Some configuration dependencies may need to be reviewed separately.

There's also a useful ServiceNow article that specifically mentions the "No agents are available at the moment" error and points to agent proficiency, AI Search, prompts, and orchestrator limits as possible causes:

AI Agents FAQ and Troubleshooting – ServiceNow Community

My recommendation would be to start with the agent proficiency and AI Search configuration in QA. The fact that the agent executes successfully when manually selected is a strong indication that the issue is related to how the orchestrator discovers and selects the agent.

One more thing: have you tried using a more explicit request, such as "Use Pace Summary Agent to summarize PACE12345"? If that works, it would further suggest an issue with natural-language agent discovery.

Hope this helps! Please let us know what you find.
If this resolves your issue, consider marking the reply as Accepted Solution and Helpful, so others facing the same problem can benefit too.

Thanks!

[Pooja Deshmane]

Thanks Dan.

There was some configuration missing for AI search. Compared with dev and moved the missing configuration to QA. It worked. 😊