One of our AWS bots is not logging detected and missed utterances. Where as all the new bots created in the same account are logging missed utterances in Monitoring -> Utterances section. I have checked the configuration of all the bots and it is all same.
In Monitoring -> Monitoring Graphs, I can see the graph showing missed utterances. I am failing to understand why the utterances (both missed and detected) is not appearing in the Monitoring > Utterances section. I know we need to wait 24 hours for them to appear. But it is not appearing at all even after 2 days. So if you can suggest some reasons for this, I will try to look into it.
I have made the aliases point to the latest version so no chance of utterances going to a wrong version. Thanks in advance
Utterance statistics are not generated under the following conditions:
The childDirected field was set to true when the bot was created.
You are using slot obfuscation with one or more slots.
You opted out of participating in improving Amazon Lex.
And as you mentioned, need to wait ~24 hours for data to be processed:
https://docs.aws.amazon.com/lex/latest/dg/ex-utterances.html
Related
With regards to the test suite, I've entered the userAgentId and the json key correctly and it progresses fine. It's when I start the test where the problem arises. Each utterance is read out to my Google Home. The Google Home wakes up to the "Ok Google. Turn off the colorful light ". The colorful light are off and reported the close status to the home graph. I link to the reportstate dashboard to confirm quickly that the status has been modified. After I waited a long time and finally got a timeout error. I don't know why and what else I need to do? I have two screenshots here. One is the request timeout and the other is the reportstatus dashboard.
timeout pic
reportstate dashboard of my colorful light
Timeouts with the test suite can be due to the following reason:
--The execution or query responses might be failing, or taking too much time.
--Report State implementation might be faulty.
The report state dashboard is an old tool that is not maintained anymore, hence the changes you see there might not represent what’s written to the homegraph accurately. Instead, can you try out using the HomeGraph Viewer.
I am unable to access Google Cloud DNS page.
All it shows is:
"DNS API is being enabled. This may take a minute or more."
Then it reloads and repeats showing the same message.
The API is already enabled, and the records I created works. No problem with DNS.
I need to modify records, but I can't because of this problem.
I tried opening the page in different computers and different browsers without addons, same result.
If there is a better place to ask, please do tell.
Thank you.
You should be able to access the page regardless of what computer / browser you're using.
If you cannot it's either a temporary outage which you can check here or a bug.
The only thing to do here is to contact paid support for more immediate help and if the time is something you can afford report this at Google's IssueTracker and get help for free - however it may take a few days. It is possible that only you are affected. Please describe the issue in as much detail as possible - this will expidete the process.
I have built a google actions project and published it. It has a web hook that is linked to a Google Functions with an actions sdk code behind it. Everything works fine.
However, I have noticed that there is a continuous user (with the same userId provided by the intent) that keeps access the function (guessing via the actions project). I am keeping a kind of sessions log and it keeps creating a session almost every 3-4 seconds.
Since the project is just some temporary demo of content and not really shared with the world at large, I am wondering what or who is causing this continuous access. It looks almost like some heart-beat type of check being done. Hence the question: is it something that Google does to know whether the action project is live or not? Thanks
Every 3-4 seconds seems high, but if you have published an Action that has gone through the review process Google does run a health check against it every few minutes.
I'm currently experiencing something rather weird: while migrating emails from a GoDaddy email server to a new G Suite set up for a number of users, I was able to successfully move for a couple of emails, as confirmed by Google's 'Complete' tick beside them. I was able to observe the migration too as it went on.
However, for one of the emails, the number of emails read just seems to keep increasing, and it still hasn't displayed 'Complete', but remains stuck on '99%'.
See screenshots I literally took just now below: as of the first latest screenshot, it says 'Successfully migrated 3230 emails', while stuck on 99%:
Then I hit refresh, check the status of that same account, and now it says '...3250 emails', while still stuck on 99%:
This isn't how it's supposed to behave, at least that isn't the behaviour I experienced with the previous 4 emails in that list. Ideally, it should say 'Migrating X out of fixed_amount emails'. In this case, that fixed_amount was
about 2,000 emails. It has now since passed that figure, but instead of showing 'Complete', it instead shows 'Successfully migrated new_amount' where new_amount keeps increasing.
This has been ongoing for almost 24 hours now. Honestly, I don't know if this is a bug or not. I really just need some helpful info to know if I should be concerned or not, perhaps maybe if someone else has run into this. Anyone?
Stumbled on to Google's documentation: https://support.google.com/a/answer/7032598?hl=en
To quote the 'Why does my migration look like it's stuck at 99%?' section:
You’ll see 99% when all email is migrated. After everything is
migrated, the data migration service applies any labels to the
migrated email, which can take time. When the labels are applied, you
should see that the migration is complete (100%).
You might also see this issue if the estimated number of emails to
migrate exceeds the actual number of messages. The migration will
report 99% until the migration completes. This process might take some
time.
You shouldn't be concerned. I was migrating around 29.000 emails from a personal gmail to Google Workspace gmail and the migration took 4 days (migrating only one user), from which the last 1.5 days the migration was "stuck" at 99%. No need to restart the migration, eventually it indeed finishes. I also got several error codes (e.g. 17009 - 'Generating an access token with the supplied credentials was unsuccessful...'), but none proved valid, I haven't actioned on them as, like in your case, I saw the number of migrated emails increasing.
I'm having a problem with the events I'm sending to Facebook Insights. I've got about 15 custom events I'm sending, and they all carry a data object that is pretty consistent between all the events. 10 of the events show up with the data object working fine (see graphic User Logged In/Out events), and for the rest, I'm getting "No data is available for the current selection." (see graphic Story Played/Selected events).
I believe with one event I shortened the Event Type, and the data started displaying properly. I tried this with other events, and that didn't fix the problem. Has anyone had this sort of problem before, and could you please comment about your solution?
I'm using Adobe AIR for mobile, running on Android, using the Milkman Games GoViral ANE. Another important factor here is that I'm sending these exact same events to a different analytics service - Mixpanel. All the events look correct on Mixpanel, so I'm pretty sure I'm sending them out properly. My assumption at the moment is that Facebook doesn't like something specific about some of my events.
I'm interested in any comments about this general kind of issue, regardless of platform or implementation, to see if I can figure out what's going wrong. I know my app setup is not so common, so for the sake of this question I'd like to ignore that for the time being.
Thanks in advance for any help you might provide.
I answered my own question. It turns out Facebook Insights events have a limit of 10 properties per event. Once I reduced the data being sent, the other events started tracking properly.