None of the data stores visible while creating a tool within Agent Builder (Conversational Agents)

[shirk]

Hi There, 

I just created an Playbook using Agent Builder, and I am trying to connect it to a Data Store by creating a Tool.

So under "Available Tool", I click on "Data Store+". So a new window opens up with which I can "Create Tool".

Now here is where the problem arise. 

When I click on "Add data stores", I don't see any of the data stores that I have created. I already created 2 - one that connects to a Cloud Storage and another one Big Query table (its been a couple of hours since I have created this, the indexing is already complete).

Here is the screenshot:

And below are the two data stores I have created:

Question is why are these data stores not showing up while creating a tool within Agent Builder?

[MJane]

Hi @shirk,

Welcome to the Google Cloud Community!

Once you've created your Playbook, select +Data Store to begin creating a new one. This action will redirect you to the Agent Builder page where you can follow the step-by-step instructions to create a Data Store for your application. 

You can also try this lab in  Google Cloud skills boost  to guide you with  connecting Playbook with Data Store. 

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.

[IanAtDazed]

I am having the same issue. I tried the lab you suggested, and had the same problem despite following the instructions (although the instructions are out-of-date with regard to the UI, so that may have confused matters.)

Here are the steps I've taken in my real application:

1. Navigate to Conversational Agents (https://conversational-agents.cloud.google.com/)
2. Click Tools from the sidebar.
3. Create a Data store tool.
4. Save it.
5. Click Add data stores in the tool's Data stores section.
6. The Add data stores panel opens.
7. Click Create new data store in the panel.
8. A new browser tab opens (https://console.cloud.google.com/gen-app-builder/data-stores/create) where I created the data store and it appears in the list.
9. Open the Conversational Agents tab again and refresh the list in the Add data stores panel - no data stores are listed.
10. Refresh the page - no data stores are listed.

Either there is an issue where the playbook is not picking up the data stores, or the process is very unintuative. Either way, it would be great to have a solution to this because currently I'm stuck.

Kind regards

Ian

[arnaudknobloch]

Hi. Same here. Any workaround?

[an2]

Same problem. While I follow the steps exactly - I can't see a newly create Data Store in the Add data stores dialog

[an2]

Ok, I may have an idea. Make sure you create your Data Store in US (not global) region.

And yes, while global is a default system suggests (EVEN when creating Data Store from Convesational Agents) - it is actually NOT supported. 

[IanAtDazed]

I have the same problem. I've tried creating my data store in the global region and then the US region. In either case, I can see it listed in the main data stores pane, but it doesn't show up in the "Conversational Agents" -> "Create Tool" -> "Add data stores" side pane. I've tried refreshing the pane and refreshing the main page, but still I don't see it. It's quite frustrating!

[IanAtDazed]

So, I've found the reason for my issue. I had created a structured, JSONL, data store, and for some reason, the Conversational Agents' tool can't see it as a data store. When I created an unstructured PDF based data source, that showed up. I don't fully understand why this is the case, and I'm now looking at alternatives, but it's kind've frustrating that the console doesn't give more indication as to why it's rejecting certain data sources.

[pjayasundara]

You should create everything in the same region. otherwise they are not visible.if you create the agent for lowa region, data store should be there also. even data store globally doesnt work

[landenn_doss]

Yes I had this issue and I FOUND THE FIX!! all you need to do is make your bucket in the same region you are in, for me It defaults to global so I made a new one and made it US and boom problem fixed!