I've been trying to create a new agent in DialogFlow. I have one agent and that has problems. (Using share never adds reviewers or developers after I press save.)
So I decided to create another agent - a new agent. I enter a name, time zone, click the create button.... it turns yellow and says "saving".... and then it turns orange and says "canceled." There is no explanation or any help document I can find that identifies the problem.
So the answer is... I have no idea why it works now but it appears there are account problems.
I went to Fulfillment and noticed the inline editor was off. I tried to turn it on and it would go on and then go back to disabled on its own. Wouldn't work. Went back to look again an hour later, same problem. Went to the Share portion about 10 minutes later to try to add a developer just one more time - and this time it worked. I went to Fulfillment and suddenly inline editor is turned on.
For at least 24 hours it didn't work. My developer claimed not to have access and when I looked, nothing in Share. Now all of a sudden it's working and I was able to readd the developer.
Related
This is a bit of a weird one:
Attempting to publish a PowerApp to my site however some of the onChange events are not firing after being published. The Preview in the app is working fine, however the version published to the site does not.
I have tried restarting PowerApps, the browser, my computer, republishing after each with no luck. Anyone run into this issue before and have a solution?
Okay - After hours of messing with this I got it to work but the solution doesn't resolve the bug, just gets my desired result.
What I was doing:
Specifically what is happening I am using an onchange event from a dropdown to assist in naming the title of the same list item.
OnChange: UpdateContext({varNewName: "example text"})
However, the title box simply wouldn't update after being published. In the preview mode in the developer environment it was running fine.
I decided to duplicate the box for laughs, tested it, both updated in preview mode just fine.
Published it and the original box was now working, the second box however was now doing nothing. If anyone knows why this is happening I would love to know, it is driving me nuts.
TLDR: If you are having this issue duplicate the recieving end of your trigger and it might resolve. ¯\_(ツ)_/¯
Same issue with rating control.
After a long day, I changed default value of binding source from Blank() to Zero. And it works fine!
I am having a strange issue that I think might be Chrome related but wanted to post here for thoughts.
I have some users who when trying to log into my node.js application, they press enter or the log in button and it just sits and spins and never times out or anything. When looking at the Network tab when this issue occurred the POST never showed up. I then put some alerts on the button click with javascript and as long as the button was in the tag nothing showed up.
Completely deleting the users' profile (suggestion from Google) made it work...until chrome updated and then it happened again.
Using any other browser, no issues. Chrome Beta, the issue shows up. Chrome Canary, I have had 2 users testing for over a week and they have not seen the issue reappear. Incognito has the issue occur as well.
Google Support asked me to send a HAR file to them. The interesting thing was when I opened up developer tools, went to the network tab and then cleared the screen to start a recording, the issue disappeared for that moment only.
It is working for 80% of my users so I can't see how it could be a coding issue, this is also a login that I created over a year ago and have not touched since.
If anyone has any insights I would love to know what might be causing this.
I am trying to run through the Google Actions tutorials to play around with Google Assistant. I've started with the first Code Lab but when I get to the 6th part, step 2 and try and toggle on the Inline Editor I consistently get:
Your Google Cloud resources are still being provisioned. Please refresh the page and try again in a few minutes.
I've now been trying to toggle this on for a good two days now, so I think something else is wrong. Something else I could be missing or could check?
It is because your projects needs to be available in firebase with setup. Follow these steps and check :
Open https://console.firebase.google.com and choose your project.
On the left menu choose storage and click on get started button. Follow the steps there.
Once it is done, refresh your dialogflow console and check again.
2 days ago the integration between Google home and API.AI agent worked perfectly. Since yesterday, when the API.AI was updated to include Google Assistant integration instead of Google Home, i had to do some extra steps on Action on Google console to make that integration work again.
But when i click on "Fulfillment" on API.AI menu, then "Google Assistant", i get the following screen:
enter image description here
But when i click on "update" or "test" i get the following error message: "Request contains and invalid argument".
How can i solve this?
Unfortunately, I too had to recreate with a brand new agent. Here's the steps I took that may help others who venture down this path...
Create a new Actions on Google project from the console: Actions on Google console
Create a zip file of just your intents and entities folders. They need to be in the top level of the zip file. (agent.json seems to be the one file that kept blowing up my agent after Google updated everything)
Create a new Agent in API.ai as you normally would
Save and finish up the "Actions on Google" console setup for the new project
Go back to API.ai and click on "Integrations" and "Actions on Google". This will allow you to click on "Update" and hopefully test the generic beginning of the agent successfully.
Finally, once you have tested the generic agent, import the zip file you created earlier and all "should" work fine. You'll have to update your fulfillment server if using one, etc.
The above works as of the morning of May 23, 2017. Good luck!
Link to previous issue: Gmail contextual gadget broken
Yesterday we received a couple of customer complaints regarding our Gmail gadget. They claimed that it had gone missing from their account. This morning, several of our employees have reported the same although, this isn't happening for everyone.
We haven't made any changes to the gadget and since it loads for some, I don't think this was caused by us.
What happens:
The window of the contextual gadget does not appear in the main Gmail interface
The window of the contextual gadget does not appear when opening an email in a new window (shift + click). This differs from when this happened previously.
We've also contacted Google and they have responded that they are looking into the issue. We've also seen that the shift-click to open an email in a new window doesn't work as a work around this time.
The last time this happened our monitoring showed that about 10% of users lost their access to the gadget per-day. We seeing a similar drop off in activity this time around.
Here are the details of the response I received from Google for this issue
Thank you for contacting Google for Work Support. I understand that
that you Gmail Contextual Gadgets have disappeared again from the
Gmail web interface.
I notice there are other user reporting a similar behavior hence he
have requested an update from our Eng team and I am currently waiting
for their response. As soon as I have an official response, I will be
contacting you back directly with the next steps.
Also I notice you mentioned that the previous workaround is no longer
working. Previously the workaround provided was to press "Shift" and
then click on the email. The email will be opened in a new window and
then the gadgets should be displayed. Can you please confirm if the
above workaround is working or not?
I’ll keep this case open while I wait for your reply. If you have any
other questions or additional comments, don’t hesitate to reply and
I'll be happy to continue helping you.
Sincerely,
Wilmer Google for Work Support
Here is the latest update from Google
As before this issue appears to be UI based as opposed to any problem with the Contextual Gadget API itself, we've gathered some troubleshooting information from affected test environments and are working on identifying a clear root cause and then remedying the behaviour at the moment.
There isn't any further you need to do on your end, I'll update you as I learn of any changes in the status of this behaviour.
Regards,
Patrick