Dialogflow training tab has suddenly stopped displaying user phrases - dialogflow-es

Training tab that has always shown user phrases is suddenly empty. Support has not responded. Logging out and back in and clearing cache, and exporting/reimporting the agent has done nothing to solve it. Someone else already asked this question here but i can't upvote that one, or comment, and if i star it but they have already moved on because it's fixed for them it's not much help.
Dialogflow "Training" menu is empty always
Has anyone else experienced this and resolved it? We are on standard V2 edition for the last year-ish. Just started being empty last week. We can see questions coming in on the history and analytics tabs but the training tab remains empty. We average 10k questions a week.

There was nothing we could do on our side to fix this. Support finally got us a solution but did not provide any details over what had caused the issue. I asked for more info but all I got was this:
Hi Vanessa,
Thanks for reaching out to Dialogflow Support.
There was some internal issue which was resolved.
We will conduct an internal investigation on the issue and make appropriate
improvements to our systems to help prevent or minimize future recurrence.
Please accept our apologies for the inconvenience.

Related

How do I force learning in the new UI when utterances are shown as Not Learned?

I want there to be a way to force these two items to become learned or at least to reveal to me why they are not Not Learned. But I can't figure out what if anything I am supposed to do.
I have run into this a couple of times where I was "sure" my training was correct, yet I got the "not learned" status
I suggest you check to see if runs properly using the "Aligned NL" feature in the V2 training when you choose Run in the Simulator
If that works, the fix I'm using might work for you.
I found that if I add a vocab to work with my enum, then my training gets learned
When training utterances aren't being learned, odds are that there are conflicting examples that Bixby cannot reconcile.
In this case, I would recommend first attempting to teach Bixby a few "follow" utterances until you can confirm Bixby is able to learn that. Then, attempt a few "unfollow" utterances. If the previously learned "follow" utterances become unlearned, the "follow" and "unfollow" utterances are conflicting.
I would also recommend that you look through the training documentation as it explains the nuance of training Bixby.

Usage of $Knowledge.Answer[2] or $Knowledge.Answer[3] in Dialogflow

While using Knowledge Base in Dialogflow, $Knowledge.Answer[1] is returning a response whereas $Knowledge.Answer[2] or $Knowledge.Answer[3] are not working. Any idea?
According to googles Dialogflow documentation.
You can see from the documentation that , Multiple responses are triggered only when you have multiple answers for the same question. And how do you give multiple responses?
Well this bugged me a lot too. But it is simple. Just give the same question twice with different answer or give a slightly different question with different answer.
Example(FAQ.txt / UTF-8):
How big is google?,Google is the universe.
How big is google?, It is the biggest in the world.
Now go to Dialogflow console and type in this question. And tada. You get two responses.
This is a sample response which I am getting for the question I asked.
So Knowledge.Answer[1] and Knowledge.Answer[2] and so on, is triggered only when there are multiple answers to that question.
Hope this helps.
There's a Bike Shop sample on Github that gives a walkthrough of how to get knowledge connectors setup for your agent via uploading a .csv file as the data source.

Getting Stock Price Data

Now that the Yahoo and Google API is down and it's not possible to retrive stock pricing data from those webistes, what other alternatives are there and how do I go about it?
This is the error I got:
raise ImmediateDeprecationError(DEP_ERROR_MSG.format('Yahoo Daily'))
pandas_datareader.exceptions.ImmediateDeprecationError: Yahoo Daily has been immediately deprecated due to large breaks in the API without the introduction of a stable replacement. Pull Requests to re-enable these data connectors are welcome.
Thanks for your help!
The GitHub issue pretty much states what's up.
"Yahoo changed their API so that the old pandas 0.5 code did not work. If you would like to fix this, PRs are welcome."
There was a major break in the API used for pandas datareader, likely due to some API changes - they are accepting PRs on GitHub to fix this. There's an open issue here: ImmediateDeprecationError:

Trouble recognizing one word intents

I'm using wit to recognize different intents in a retail context. Some of them trigger (successfully) FAQ answers, other initiate a business logic.
Surprisingly, I'm having a lot of trouble with the most basics conversational intents, like answering a hi or hello. Specially if they come as a single word (it doesn't get hi or hello but it successfully returns the correct intent for hi buddy or hey dude). Obviously there's a high chance that the first thing an user would say is just a simple hello, any of you found the same issue? Any guidance on that?
It is actually the first time I experience this issue, and I haven't heard about it. Could it be related to the increasing number of intents created (now 15+)? I'm using trait as a search strategy.
Greetings intent
Click on image for a larger version of the image.
Thank you very much for your help,

wit.ai is not training new examples / training status stays "clean"

yesterday I added a bunch of new training examples to my wit.ai-Project but the training status got stuck somehow. The status always stays "clean" (green icon) when i add new examples – it seems, that the training process can't get triggered anymore. Thats pretty annoying, because none of the new examples work.
Can anybody help? Am I doing something wrong? (If someone at wit.ai reads this: Project name is ts_bot_dev_1).
According to Wit.ai Hackers FB Group , there were some issues with training services in Wit the past couple days. It should be fixed by now.

Resources