Posting to https://graph.microsoft.com/v1.0/communications/callRecords/{id} is giving a 404 error

Question

Posting to https://graph.microsoft.com/v1.0/communications/callRecords/{id} is giving a 404 error

Matt Ringsell 25

When I am running https://graph.microsoft.com/v1.0/communications/callRecords/{id} it gives a 404 error for all call ID's after 22/05/2024 13:25:24 (BST). If I run the same on call ID's before this time I get no errors.

Invoke-RestMethod : The remote server returned an error: (404) Not Found.

$resp = Invoke-RestMethod -Method get -Uri $url -ContentType "applic ...
```
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
- CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
- FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

JimmyYang-MSFT 58,576 Reputation points Microsoft External Staff

2024-05-23T02:38:35.4133333+00:00

Hi @Matt Ringsell

Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your issue is more related to Teams development, which is not in our support scope. So I will remove teams tag from your thread. Thanks for your understanding!
Haydn 5 Reputation points

2024-05-23T04:05:29.55+00:00

@Matt Ringsell I had the same issue in the same timeframe.
I have been running a service that receives the Notifications, logs the details and then looks up the callRecord information against the Microsoft Graph API and it's been working correctly for months, but during the same period of time you have logged in your question, I was still receiving the Notifications of Created and Updated callRecords but when attempting to get the details of the callRecord from the Graph API it was erroring with a 404 and the message "Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available." which is not the case as the call Notification had only just been received.

I have since re-processed the exact same records to get the callRecord details from the Graph API and they are now correctly returning details, so the issue appears to be resolved now, but there was definitely an issue during that period of time on Microsoft's side, which was incorrectly returning a 404 for recent records, so it would be good to determine the root cause and ensure awareness of the issue.

@JimmyYang-MSFT here are the request details for the failed requests (these have since been reprocessed succesfully) which should allow you/the Microsoft Team to investigate the cause of the issue.

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T12:53:06 request-id: 02aa3b77-c74c-44be-80aa-ba4aec528bea client-request-id: 02aa3b77-c74c-44be-80aa-ba4aec528bea ClientRequestId: 02aa3b77-c74c-44be-80aa-ba4aec528bea

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T13:44:41 request-id: 572afbe6-070e-4a7f-a1f4-9c61b4efb2e0 client-request-id: 572afbe6-070e-4a7f-a1f4-9c61b4efb2e0 ClientRequestId: 572afbe6-070e-4a7f-a1f4-9c61b4efb2e0

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T14:05:12 request-id: 279cc7e5-9cc5-4d37-a152-79e60d35afb3 client-request-id: 279cc7e5-9cc5-4d37-a152-79e60d35afb3 ClientRequestId: 279cc7e5-9cc5-4d37-a152-79e60d35afb3

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T14:08:43 request-id: 689b841d-e3a3-4197-89bb-e28ed5fe3ada client-request-id: 689b841d-e3a3-4197-89bb-e28ed5fe3ada ClientRequestId: 689b841d-e3a3-4197-89bb-e28ed5fe3ada

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T14:20:11 request-id: 64719da0-2f8d-4729-b047-f7c7b376e427 client-request-id: 64719da0-2f8d-4729-b047-f7c7b376e427 ClientRequestId: 64719da0-2f8d-4729-b047-f7c7b376e427

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T14:47:43 request-id: abe6f7f3-3fc4-46ce-bf6b-780ea29f965d client-request-id: abe6f7f3-3fc4-46ce-bf6b-780ea29f965d ClientRequestId: abe6f7f3-3fc4-46ce-bf6b-780ea29f965d

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T14:49:13 request-id: e0bf7614-32ca-447f-a8a4-64caed10a605 client-request-id: e0bf7614-32ca-447f-a8a4-64caed10a605 ClientRequestId: e0bf7614-32ca-447f-a8a4-64caed10a605

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T14:50:07 request-id: 4e1472de-afc3-4d03-a08b-3dfb59c49f62 client-request-id: 4e1472de-afc3-4d03-a08b-3dfb59c49f62 ClientRequestId: 4e1472de-afc3-4d03-a08b-3dfb59c49f62

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T14:57:12 request-id: 5cba6c9a-e51d-4784-a831-c7f0d397df00 client-request-id: 5cba6c9a-e51d-4784-a831-c7f0d397df00 ClientRequestId: 5cba6c9a-e51d-4784-a831-c7f0d397df00

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T15:16:16 request-id: d46df7cf-b652-4059-bec9-c8743ccb4b53 client-request-id: d46df7cf-b652-4059-bec9-c8743ccb4b53 ClientRequestId: d46df7cf-b652-4059-bec9-c8743ccb4b53

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T15:18:13 request-id: 424ad59e-ad86-47b9-b94f-bbf2cef6d094 client-request-id: 424ad59e-ad86-47b9-b94f-bbf2cef6d094 ClientRequestId: 424ad59e-ad86-47b9-b94f-bbf2cef6d094

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T15:30:44 request-id: c09d7a7b-d618-4ed9-9ff6-1df11d83c6af client-request-id: c09d7a7b-d618-4ed9-9ff6-1df11d83c6af ClientRequestId: c09d7a7b-d618-4ed9-9ff6-1df11d83c6af

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T15:33:44 request-id: 43adb890-2ff7-4de9-8546-426807773547 client-request-id: 43adb890-2ff7-4de9-8546-426807773547 ClientRequestId: 43adb890-2ff7-4de9-8546-426807773547

Code: NotFound Message: Could not find the requested call record. Records about calls or online meetings that started more than 30 days ago are not available. Inner error: AdditionalData: date: 2024-05-22T15:35:44 request-id: 53b8b688-ce80-467b-bfac-c5e1e069622f client-request-id: 53b8b688-ce80-467b-bfac-c5e1e069622f ClientRequestId: 53b8b688-ce80-467b-bfac-c5e1e069622f
Matt Ringsell 25 Reputation points

2024-05-23T06:12:01.04+00:00

Glad to know it’s not just me.
Prasad-MSFT 8,876 Reputation points Microsoft External Staff Moderator

2024-05-23T07:11:10.6333333+00:00

Hi Matt Ringsell - Are you still encountering this issue?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Haydn 5 Reputation points

2024-05-23T07:30:18.3933333+00:00

@Prasad-MSFT using the details in my comment above, can the issue please be investigated to determine root cause and hopefully prevent from recurring?
Matt Ringsell 25 Reputation points

2024-05-23T12:55:11.32+00:00

@Prasad-MSFT Yes it's operational now, but it was down for 14 hours, so is there a case open in Microsoft I can reference, please of the service behavior and outage.
Prasad-MSFT 8,876 Reputation points Microsoft External Staff Moderator

2024-05-27T06:36:07.29+00:00

Thanks for confirming. We have shared the above details with engineering team to get the root cause of failure and if there is any case open for this. We will inform you once we hear from them.

1 answer

Your answer

JimmyYang-MSFT 58,576 Reputation points Microsoft External Staff

2024-05-23T02:38:35.4133333+00:00

Hi @Matt Ringsell

Teams tag is mainly focused on the general issue of Microsoft Teams troubleshooting. According to your description, your issue is more related to Teams development, which is not in our support scope. So I will remove teams tag from your thread. Thanks for your understanding!
Matt Ringsell 25 Reputation points

2024-05-23T06:12:01.04+00:00

Glad to know it’s not just me.
Prasad-MSFT 8,876 Reputation points Microsoft External Staff Moderator

2024-05-23T07:11:10.6333333+00:00

Hi Matt Ringsell - Are you still encountering this issue?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Haydn 5 Reputation points

2024-05-23T07:30:18.3933333+00:00

@Prasad-MSFT using the details in my comment above, can the issue please be investigated to determine root cause and hopefully prevent from recurring?
Matt Ringsell 25 Reputation points

2024-05-23T12:55:11.32+00:00

@Prasad-MSFT Yes it's operational now, but it was down for 14 hours, so is there a case open in Microsoft I can reference, please of the service behavior and outage.
Prasad-MSFT 8,876 Reputation points Microsoft External Staff Moderator

2024-05-27T06:36:07.29+00:00

Thanks for confirming. We have shared the above details with engineering team to get the root cause of failure and if there is any case open for this. We will inform you once we hear from them.

Answer 1

CarlZhao-MSFT 46,341

Hi @Matt Ringsell

Call records are only kept for 30 days, if your call records are older than 30 days, then it will return a 404 response.

User's image

If your call records are up to date but you are still receiving a 404 error, this may be an unknown error. I recommend you report this error to MS Graph or open a support ticket.

Hope this helps.

If the reply is helpful, please click Accept Answer and kindly upvote it. If you have additional questions about this answer, please click Comment.

Matt Ringsell 25 Reputation points

2024-05-24T09:27:33.8733333+00:00

We are aware of this, but that is not the fault.. If Microsoft is telling us to collect a call record for TODAY and we are getting a 404, that's a Microsoft fault. Please can you re-read the above and investigate the requests sent?

Share via

Posting to https://graph.microsoft.com/v1.0/communications/callRecords/{id} is giving a 404 error

1 answer

Your answer