Have a weird case. I have configured Amazon Lex Bot (V2) and have created Twilio Channel to integrate with WhatsApp. The Bot is working all fine on WhatsApp. I have enabled Text Conversational logs and see that the logs are recorded only for one mobile number whereas logs are not recorded for any other mobile numbers. Do we need to do any more configuration to log all the users conversational logs?
Many thanks
The logs started appearing fine now. Not sure what could be the issue. Since I am able to see the logs now, marking this as closed. Technically no changes are made, same old setup was working fine.
Related
Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.
I'm trying to generate alerts based on notifications from Taiga project management software (when a user creates a project for example). These alerts will arrive to a specific Rocket.chat channel.
For this I am using the incoming Rocketchat webhooks: https://docs.rocket.chat/administrator-guides/integrations/
So I created the incoming webhook and entered the data into Taiga:
Configuring the webhook in Taiga
Once all this is done I check that the message arrives at the destination correctly:
Example of a notification message
Indeed, the message is received but it doesn't show any information. When a user history, an issue or any modification that leads to an alert is created, it is received in rocketchat but it doesn't show any information (empty message).
Payload sended by Taiga to Rocketchat
Does anyone know why he won't show me any information?
Thank you very much in advance
Greetings.
Do you really want to post notifications to a Rocket Chat channel, when a taiga user created a project in taiga? I would not know, how you can do that. But, as far as I can see, your screenshot shows the configuration of a generic webhook in a project after that project has been created. Therefore, I hope it is sufficient to post notifications from that project to your Rocket Chat channel. Here is my answer for this case:
I observed a similar behavior. Using the generic webhook, I could only trigger empty posts in my Rocket Chat channel by clicking on "test" for that webhook.
However, the Rocket Chat API seems to be compatible with the Slack API, cf. https://github.com/RocketChat/Rocket.Chat/issues/1728#issuecomment-166669379.
In contrast to the generic webhook, the Slack plugin for taiga (https://github.com/taigaio/taiga-contrib-slack) worked out of the box (https://tree.taiga.io/support/contrib-plugins/slack-integration/).
Only my browser gave me some hassle, because it cached the taiga webpage and after installing the Slack plugin a simple page reload was not enough to display the "Plugins" entry in the "Admin" menu of the project. "Shift+reload" did the job. But apart from that standard issue, everything worked.
We have a simple hangouts bot that has been working fine for several months. Starting yesterday 1 or 2 users indicated that they were receiving an error message when talking to the bot indicating that: 'Your administrator prevented you from talking to bots in direct messages'. Over the past 24-hours more and more people reported that the issue started happening to them until it was everyone. When it happened to me earlier today I messaged the bot 2 times about 5-minutes apart, it worked the first time then the second time I got the administrator prevented message.
I tested the #meet and #drive bot's and they both still appear to work.
I have confirmed that none of the settings on the bot have changed, most importantly that the 'Bot works in direct messages' option is still checked.
I have talked to our IT administrator who says that no settings have changed in our GSuite setup.
Looking through the documentation I can't find any mention of an issue or setting that would cause the above error. Is anyone aware of what could be causing the above.
Google Support statement
(...) if your domain currently applies a whitelist to restrict the set of G Suite Marketplace apps that users can install, existing internal bots may stop working. In order to appear and continue to function for users, the developers of these bots need to publish the bots to the domain as you can see on link. (...)
Solution
As said Jordansan this issue is related to the domain administration and to security enhancements. You may still use up to 5 email addresses to do your tests. Once you want your bot public, you will need to list it on the G Suite Marketplace.
To do so follow this guide Listing your bot on G Suite Marketplace. An extract is provided below :
G Suite Marketplace publication steps
This section tells you the specific steps you need to perform to publish your bot on G Suite Marketplace. The general steps are:
Create an OAuth client ID, if your project doesn't already have one.
Add the G Suite Marketplace SDK to your project and populate its configuration tab.
Populate the SDK's publish tab and submit.
The detailed steps for each of these are described in the following paragraphs.
For security reasons most organizations have (and should have) whitelisting enabled, which will prevent non white-listed marketplace apps to be enabled within the organization.
To deploy your bot you'll need to contact your GCP responsible and ask him to whitelist your bot.
Temporary solutions
What you can do is make the bot accessible to everyone in your organization. Assuming that the bot can be published.
If the bot shouldn't be public, you may implement your own connector to filter incoming queries and allow only selected email addresses. However the bot will still appear to everyone on the search screen, and everyone will be able to message it.
It's possible that your domain makes use of a new feature which requires bots to be whitelisted. This was introduced in a recent update. Previously, the admin setting was binary in that you could allow either all bots or none. Now any second party bots must be whitelisted if the administrator settings for that domain requires whitelisting.
You can find more information here: https://support.google.com/a/answer/6089179
I opened a ticket here: https://issuetracker.google.com/issues/137266964
Edit: We got this working by following the steps listed here: https://developers.google.com/hangouts/chat/how-tos/gsm-list and our GSuite admin white-listed the Bot for internal use. This eliminates the 5 user limitation and keep the current security settings in place for all other bots & GSuite Applications
I am developer and maintainer of an Angular web app which uses Google OAuth. This works normally.
Last week the app users (me including) started receiving standard Security alert emails from Google (no-reply#accounts.google.com) on a daily basis. The Email says "Appname was granted access to your Google account". This is of course bad signal to the users.
When clicked on "Check Activity" in the Email it always says:
Unrecognised device
X hours ago
Unknown (location)
This is the case for all users tested on many different devices and IPs.
Recently I have upgraded from Angular 5 to Angular 7 if that might help.
Also recently I noticed absolutely the same behaviour when I sign-in to Dropbox using a Gmail. The application I am responsible for is not storing session data for privacy reasons so the users are asked to Sign-in with Google every time they want to use the app. I noticed this behaviour just a week ago (devices and locations not recognised) by Google.
The google group (https://groups.google.com/forum/#!forum/oauth2-dev) redirected me to Stackoverflow. Any help is much appreciated! :)
We are sending notifications to users when they approve certain scopes. That list is expanding and more apps will see the notification.
Thanks for the feedback. Looks like the unrecognized device was an issue and we have rolled back that experiment.
Ideally an app should see the notification only once and for non basic scopes (basic scopes being email, profile etc).
I have followed the instructions as per the https://developers.google.com/hangouts/chat/how-tos/bots-develop?authuser=1
Created my agent - named as "phoebieagent".
Defined intents and entities.
Fulfilled by webhook and running a flask python API on https.
Published by bot as hangouts chat. Specified bot url to be the one
defined in step 3.
Bot status shows - "live" but in my hangouts I can't see my bot user.
Please suggest trouble shooting steps.
Thanks
Resolved it. Chat was disabled in google admin console.