I'm trying to use a DeltaLink to get Event changes from a Calendar. It works good but sometimes I get an HTTP 400 - ErrorCannotUseItemIdForFolderId error.
Oddly enough, I get a success response when I send the same DeltaLink the next day.
What's wrong with this DeltaLink?
Request:
GET https://graph.microsoft.com/v1.0/users/{id}/calendars/{id}/calendarView/delta?$deltatoken={token}
Response:
"error": {
"code": "ErrorCannotUseItemIdForFolderId",
"message": "Expected a folder Id but received an item Id.",
"innerError": {
"request-id": "a704ea5f-2677-4f38-88c0-aaca240b4cb8",
"date": "2019-05-30T16:40:46"
}
}
Related
When trying to get the range of the table using Graph API /items/{workbookId}/workbook/tables/{tableName}/range?$select=address, we are getting an error immediately with the following details
{
"error": {
"code": "MaxRequestDurationExceeded",
"message": "We're sorry. We couldn't finish what you asked us to do because it was taking too long.",
"innerError": {
"code": "gatewayTimeoutUncategorized",
"message": "The service wasn't able to complete the request within the time limit.",
"innerError": {
"code": "MaxRequestDurationExceeded",
"message": "We're sorry. We couldn't finish what you asked us to do because it was taking too long."
},
"date": "2023-01-06T14:45:21",
"request-id": "4b6b5b18-e879-451a-b480-107a29240f19",
"client-request-id": "4b6b5b18-e879-451a-b480-107a29240f19"
}
}
}
We have verified that data in the Excel is within the limits provided in this link
We have product that writes data to Excel on schedule. As part of that solution, we read the range of the table and clear it before writing. When we make a request to get range, it should return the proper range instead of error
When I execute a request for a specific callRecord like this it works:
https://graph.microsoft.com/v1.0/communications/callRecords/{id}
But when I do this I get an error (500):
https://graph.microsoft.com/v1.0/communications/callRecords/{id}?$expand=sessions
{
"error": {
"code": "InternalServerError",
"message": "Object reference not set to an instance of an object.",
"innerError": {
"date": "2022-04-14T12:21:34",
"request-id": "{guid}",
"client-request-id": "{guid}"
}
}
}
It looks like this doesn't happen for every callRecord though. We started seeing this error in our logging around 2022-04-11T00:24:00Z, now we get thousands of those.
It was an internal issue on Microsoft's side. Everything seems to be fixed.
When accessing data using https://graph.microsoft.com/beta/teams/{id}, it is failing with 400 bad request without any error details. {id} is the value received from the response of https://graph.microsoft.com/beta/groups.
Following response is returned.
{
"error": {
"code": "AuthenticationError",
"message": "Error authenticating with resource",
"innerError": {
"date": "2021-10-15T15:01:43",
"request-id": "1d82fe40-5186-46fc-9fb7-c16341eb1ffb",
"client-request-id": "29c9e68d-bfd8-6f53-65c4-c49a82581a76"
}
}
}
We tried using MS graph SDK as well as graph explorer. All the consent are given for the end point.
What could be the reason for the error?
I have an active GraphAPI subscription to /communications/callRecords which is successfully returning the callid for calls. When attempting to get the call details using the following request:
https://graph.microsoft.com/beta/communications/callRecords/45578cfe-8329-48b7-ba6b-54a627b00bf4?$expand=sessions($expand=segments)
I receive the following error:
{
"error": {
"code": "BadRequest",
"message": "Unsupported segment type. ODataQuery: /communications/callRecords/45578cfe-8329-48b7-ba6b-54a627b00bf4",
"innerError": {
"date": "2020-11-24T12:34:11",
"request-id": "277b4fa1-11a5-4922-94d7-83fec3a57572",
"client-request-id": "277b4fa1-11a5-4922-94d7-83fec3a57572"
}
}
}
I get the same error if I change the GraphAPI call to /v1.0/. I am sure this worked previously but can't seem to work out what may have changed.
POST https://graph.microsoft.com/v1.0/me/messages/AAMkADFkZDdjMWM0LTg2MzYtNGI4ZC1hNDAzLWY2NDljZmZmZDM4YQBGAAAAAAAy50dDcjLxRroxR16zN80WBwAqP1cdrk5dTLdAWYlr7M8QAAAAAAEPAAAqP1cdrk5dTLdAWYlr7M8QAAChu4WSAAA=/send
Suddenly started throwing this now (first it was seen on the beta endpoints. Now it is coming on v1.0 as well
{
"error": {
"code": "InternalServerError",
"message": "Object reference not set to an instance of an object.",
"innerError": {
"request-id": "eecf9817-1c44-4fa5-aabb-f975f8496484",
"date": "2016-09-25T09:16:43"
}
}
}