search

dialogflow / dialogflow-nodejs-client

Node.js SDK for Dialogflow
Apache License 2.0
659 stars 287 forks source link

Recently Added Intents are not being triggered #119

Closed agnescameron closed 4 years ago

agnescameron commented 4 years ago

Hi there --

I've been trying to debug a problem with our agent for a while now, and have been running up against a mysterious error. I'm interfacing to DF using the NodeJS client, which is why I've posted the issue here, though I believe the issue might lie with the platform itself (if there's a better place to post this, please advise).

None of the intents that I have added in the past week are being triggered when a text that matches a training phrase is entered. Currently, I am creating new intents using the web console interface, and then communicating with the bot using the nodeJS API.

I have tried modifying the lifespans of the context to make sure they are not interfering with one another, and also have ensured that the text on each intent is sufficiently specific as to prevent interference.

The most recent test I have tried is to run a query in the Dialogflow console itself, having reset all contexts. (I also notice the mysterious appearence of a context called __system_counters__, which I don't believe was there before) The results are shown below: despite the query being a verbatim training phrase (the training phrases are specific, and definitely dissimilar to training phrases for other intents for this agent).

image

I do not believe that this project has exceeded a quota limit. There are currently around 25 intents, and fewer than 20 training phrases per agent.

All previously written intents continue to work fine, and I am able to change and update training and response phrases without issue.

The only issue I can think of that has changed the account in the past week or so is that we created a service account that can manage multiple agents simultaneously. This is necessary for our application, as we're running a serverless site which can only store one private key as a process variable. This itself was discussed on the Google forums, and was a solution that others had successfully used. I can't think why that would affect the adding of intents, though, especially as everything else continues to work as expected.

Thanks!

agnes

agnescameron commented 4 years ago

realised this is the wrong repo! closing.