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

Attached website datastore is not working in DialogFlow CX

I created a chatbot using dialogFlow CX and using datastore created with website indexing data.

The website indexing in datastore was done successfully and i also tested it completely (it was working as expected).

But, Suddenly it is going to no-match default event handler and not able to find any data from the attached website datastore.

Any kind of help will be appriciated.

1 REPLY 1

Hi babuharsh,

Welcome to the Google Cloud Community!

Here are a few approaches that might help you diagnose why your Dialogflow CX website datastore isn't working:

  • Test simple queries like 'What is your return policy?' or 'What are your accepted payment methods?' to check datastore connectivity. If they fail, it's likely a connectivity or configuration issue. This could include firewall rules blocking access from Dialogflow CX to the Data Store, or incorrect project ID configured in Dialogflow CX's knowledge connector settings, or missing permissions for the Dialogflow CX service account to access the Data Store. If only complex queries fail, it's a query matching problem.
  • Ensure there are no ongoing service issues by reviewing the Google Cloud Status Dashboard.
  • Check Dialogflow CX logs and Cloud Logging for errors or unusual activity.
  • Create a basic test flow in Dialogflow CX that interacts only with the Datastore to rule out interference from other parts of your agent.
  • Use the API Explorer or curl commands to directly query the datastore and test it independently. This bypasses Dialogflow CX entirely, allowing you to confirm the datastore is functioning correctly and contains the expected data.
  • Try re-indexing a smaller part of your website. If you have control over the website's structure, create a separate directory with just a few sample pages and configure the Data Store to only index that directory. This allows you to quickly test the indexing process. Allow some time after re-indexing to account for potential caching.
  • Finally, check the quality of the indexing and search settings in the Data Store itself. Incorrect settings here can lead to no matches, even if the data is present.

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.