Welcome to the RingCentral Community

I thought it was fixed a long time ago. But I just checked and it wasn't.

Let me check with the platform team to get the latest status.

UPDATED: Unfortunately, the issue is not fixed and I have no ETA.

Yes. Here's what I see no matter the what record ID I check:

And here it is in the admin call log report:

I meant to say no matter what recording Id I check.

Hi Daniel,

Did you receive any resolution to this issue? We are facing the same problem.

Nope... It took an entire week to get their dev support team to do a screen share with me and for them to admit it was an issue on their end. This was their most recent response:

Hi,

Sorry, we do not have an ETA yet, we gathered a couple of other cases with customers being impacted by this and escalated to our Ops team.

Just an FYI, these kind of bugs take a while to get prioritized, fixed and then deployed across all the pods. Just making sure I set the correct expectations.
This is not directly linked to the APIs, so the core teams have to be involved.

Thanks,
RC Dev Support

Thanks. I received a similar response, although the issue has only appeared for us within the last few days.

As a workaround I am using the call log endpoint to get the call duration:

/restapi/v1.0/account/accountId/extension/extensionId/call-log

Yeah, we don't do auto-recording because there's some compliance concerns that we need to deal with live before we're allowed to start recording, so the call duration for us is never the same as the recording duration.

I found a ticket reporting the same issue for other accounts. So it looks like there is an issue on our platform and the engineers are working on it. I will keep tracking the ticket and let you know when the issue is resolved.

Will give you update when I get more info from the platform team.

Has there been any movement on this issue? We have had the same issue and are watching for feedback. Pressure to resolve this is growing as this is an issue at a few of the sites we work with

We've not received any update other than the teams are looking into it. Issue first occurred on the 1st June for us.

As a workaround I am using the call logs endpoint to get the call duration to determine whether we need to download the recording.

That's weird. I just check and it returns the correct value

{
  id: '197253472xxxx',
  contentUri: 'https://media.ringcentral.com/restapi/v1.0/account/80964xxxx/recording/197253472xxxx/content',
  contentType: 'audio/mpeg',
  duration: 87
}

I suggest you open a dev support ticket so some one can have a closer look at your account. I am sure that it's not the platform issue.

thanks @Phong Vu , I opened one yesterday. No response.