Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Agent Builder is intermittently unresponsive when publish agents.

I have successfully developed an agent that connects to an unstructured datastore. However, upon deploying it to integrate with my website, I'm encountering an issue where the agent occasionally becomes unresponsive when I query about information stored in my documents within the datastore.

Screenshot from 2024-12-31 11-12-35.png

Instead of providing an informative response like "Sorry, I couldn't find information related to this question" it remains unresponsive."

Solved Solved
0 1 84
1 ACCEPTED SOLUTION

Hi @diepphan,

Welcome to Google Cloud Community!

It sounds like your agent is encountering an issue when querying the datastore, leading to it becoming unresponsive instead of returning an appropriate error message. 

The agent might not have proper error handling or fallback mechanisms in place. When it doesn't find the relevant data, instead of returning a message or performing an alternate action, it simply fails to respond. Here’s what you can consider:

  1. Implement Default Responses: Ensure the agent always provides a response, even if it cannot find relevant data. For example, when no information is found. (e.g. Sorry, I couldn't find any information related to that question)
  2. Enhance Query Error Handling: If the datastore returns no data for a query, ensure that the agent can identify this scenario and generate a meaningful fallback response. You can detect empty or null results and handle these cases with a specific response.

You can refer to the following documentation for more details:

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

View solution in original post

1 REPLY 1

Hi @diepphan,

Welcome to Google Cloud Community!

It sounds like your agent is encountering an issue when querying the datastore, leading to it becoming unresponsive instead of returning an appropriate error message. 

The agent might not have proper error handling or fallback mechanisms in place. When it doesn't find the relevant data, instead of returning a message or performing an alternate action, it simply fails to respond. Here’s what you can consider:

  1. Implement Default Responses: Ensure the agent always provides a response, even if it cannot find relevant data. For example, when no information is found. (e.g. Sorry, I couldn't find any information related to that question)
  2. Enhance Query Error Handling: If the datastore returns no data for a query, ensure that the agent can identify this scenario and generate a meaningful fallback response. You can detect empty or null results and handle these cases with a specific response.

You can refer to the following documentation for more details:

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.