I have added intent through Dialogflow(v2) PHP API https://cloud.google.com/dialogflow/docs/manage-intents, and i am able to see them on dialogflow console as well. but when i try to search with added intent DF shows "Internal Server Error", while looking at "Diagnostic Info" show below error:
{ "id": "d60722ee-6060-41ac-8984-884e471c77d3", "timestamp": "2020-01-27T08:51:44.575Z", "lang": "en", "status": {
"code": 500,
"errorType": "internal_server_error",
"errorDetails": "Internal Server Error",
"errorID": "2def8f3a-c0f1-46bb-b23e-8746b8839164" }, "result": {} }
Is this related to DF or something else please help!
I Got the solutions on dialogflow docs: https://cloud.google.com/dialogflow/docs/training
After adding any question on DF via API or DF we need train Agent.
Caution: For agents with more than 780 intents, you need to update the machine learning algorithm manually. To do this, follow these steps:
Click on the gear icon for your agent.
Click the ML Settings tab.
Click Train.
Related
I got quite far following the hints from Pulling Excel.xlsx workbook from Sharepoint site using Microsoft Graph API but now I am stuck and would appreciate some help.
I want to call the Graph API Excel endpoint from a Power Automate flow and first I am testing things in the Graph Explorer but cannot get beyond a point.
What works (and confirms that the file's "mimeType" is "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"):
https://graph.microsoft.com/v1.0/sites/<tenantid>.sharepoint.com:/sites/<siteid>:/lists/<listid>/items/19/driveitem
But when I try this:
https://graph.microsoft.com/v1.0/sites/<tenantid>.sharepoint.com:/sites/<siteid>:/lists/<listid>/items/19/driveitem/workbook
... it generates error:
{
"error": {
"code": "-1, Microsoft.SharePoint.Client.InvalidClientQueryException",
"message": "The parameter name path is not valid.",
"innerError": {
"date": "2020-10-22T08:04:16",
"request-id": "aad38960-538d-4a5b-b3c6-097d19f07b09",
"client-request-id": "a029dea8-f9f9-9a04-d4a3-7901be8d1eca"
}
}
Any suggestion?
Thanks!
P
Can you please have a try below endpoint?
https://graph.microsoft.com/v1.0/sites/<siteid>/lists/<listid>/items/8253/driveitem/workbook/worksheets
Below is my test:
When I create the actions on google project and API.AI agent, I use my own service to be API.AI fulfillment webhook. I expect that API.AI will call my webhook. But when I test it by simulator of actions on google, the API.AI always return:
"message": "Unexpected apiai response format: Empty speech response",
"apiResponse": {
"id": "905d5727-bea8-4630-8d3a-e6c173159a94",
"timestamp": "2017-09-28T02:20:06.954Z",
"lang": "en",
"result": {},
"status": {
"code": 206,
"errorType": "partial_content",
"errorDetails": "Webhook call failed. Error: Webhook response was empty."
},
"sessionId": "1506565201634"
}
But when I check the logs of apache, the API.AI did not call my webhook! When I replace the webhook url to firebace functions, it work success. But if I use my own service url to be API.AI webhook url, the API.AI do not call the webhook anyway. My service use https.
I also got this issue and I could manage to solve it. below error details were somehow misleading
"status": {
"code": 206,
"errorType": "partial_content",
"errorDetails": "Webhook call failed. Error: Webhook response was empty."
}
Actual issue was something else. I was adding output context in response from web-hook and name of context was invalid (it had a space in name). This was causing above error message.
As a general rule, it looks like that above error message will be received when response from web-hook is in invalid format.
Hope it will help someone in future.
OK, I solved the problem. The reason is the configuration of https. It should add ca in ssl options. The details of the solution see the link:
https://discuss.api.ai/t/webhook-does-not-work-with-https/6708/8
#dmulter Sometimes, if your account exceeds its quota limit then also response would be Webhook Failed.
I'm playing with the microsoft graph and especially the sharepoint beta api and i am constantly running into issues. I know its beta, but still;)
I'm getting out my expanded fields but i'm not able to select other than id.
/items?expand=fields(select=id) <-- works
/items?expand=fields(select=Title) <-- fails with response being
{
"error": {
"code": "invalidRequest",
"message": "The request is malformed or incorrect.",
"innerError": {
"request-id": "f460cded-46da-468c-a027-f027707a62fc",
"date": "2017-05-10T09:00:10"
}
}
}
Further on trying to filter the request with the request /items?expand=fields&$filter=fields/id eq '421' doesn't work and after a long period just returns a response without taken the filter into account.
Can someone respond if the experience the same or if my syntax is wrong or whatever would be nice. Thanks in advance. Ole Bergtun
i changed /items?expand=fields(select=Title) to /items?expand=fields(select%3DTitle) and it works for me.
I've been trying to do various things through your Mail REST API today and not having much success... My project (using the api) has been running for at least a month now, but requests to your api are failing.
For example:
GET https://outlook.office365.com/EWS/OData/Me/messages (works)
GET https://outlook.office365.com/EWS/OData/Me/inbox (doesn't work)
Looking at the documentation, still says its available.
Trying to send an email using:
POST https://outlook.office365.com/EWS/OData/Me/Messages?MessageDisposition=SendAndSaveCopy also just returns 400 (Bad Request)
Any info about this?
Also, the http status codes returned are not useful at all; almost all errors return as 400's. In one instance, I didn't provide auth creds, and a 400 was returned instead of the appropriate 401. The accompanying status code detail could also be more helpful.
Thanks for the feedback and sorry for the inconvenience. We are currently deploying some non-backwards compatible changes described here, and this is causing your issues. The current set of changes including versioning support, and deploying non-backwards compatible changes won't cause issues for your app in the future. For the queries, that don't work, please use the following:
Accessing Inbox: https://outlook.office365.com/ews/odata/me/folders/inbox
Send email (new action called SendMail):
POST https://outlook.office365.com/ews/odata/me/sendmail
{
"Message":
{
"Subject": "Test message",
"Body":
{
"Content": "This is test message!"
},
"ToRecipients":
[
{ "EmailAddress": { "Address": "John#contoso.com", "Name": "John Doe" }},
{ "EmailAddress": { "Address": "Jane#fabrikam.com", "Name": "Jane Smith" }}
]
},
"SaveToSentItems": true
}
Hope this helps. We are updating the documentation to reflect the changes, and it should be available shortly. Thanks for the feedback on the HTTP status codes, we will review the status codes returned currently and make any fixes required.
Conversation support is in our roadmap but we don't yet have a timeline to share. Currently, you can search using https://outlook.office365.com/ews/odata/Folders/FolderId/Messages?$filter=ConversationId%20eq%20%%27ConversationID%27 but this will only return messages within the specified folder belonging to that conversation.
Let me know if you have any questions or need more info.
Thanks,
Venkat
Am reading this page by Boris Smus and tried to implement and everything is working good. The only problem is, the requests are failing after some time. Am using googleapis. As soon as I install my test extension and try to make some googleapi requests, they are passing. But aftersome time when I try the same they are failing.
In the background.js NET tab i see the following response.
{ "error": { "errors": [ { "domain": "global", "reason": "authError", "message": "Invalid Credentials", "locationType": "header", "location": "Authorization" } ], "code": 401, "message": "Invalid Credentials" } }
If I just reload my extension everything is working fine again. Am thinking it is something to do with accesstoken but am not sure how/where to fix it.
Also what I observed from console tab of background.js page, google.isAccessTokenExpired() results in 'false' when everything is working. It returns TRUE when everything is failing. Where/How do I fix this problem.
Solved! Added the following code.
if(google.isAccessTokenExpired()) {
google.authorize(function() { myFunc(info); } );
}
Not sure why it dint't worked a while back. Now its working.
For me it worked fine for the userinfo API. But not for contacts API. The problem was solved by changing the Url for contacts from http to https
So the Url I used: https://www.googleapis.com/m8/feeds/contacts/default/full