Skip to main content

This morning RingCentral Meetings API are not function well. That results in users unable to schedule meetings AND change their PMI. There may be additional features impacted.

I went to change some settings in PMI from app.ringcentral.com and noticed that JavaScript throws an error:

Uncaught (in promise) Error: Api Error: Please check local network crash. method: get, url: https://api-ucc.ringcentral.com/restapi/v1.0/account/~/extension/~/meeting/user-settings

    at JNetworkError.JError [as constructor] (fiji-core-foundation.607749f4.min.js:1)

    at new JNetworkError (fiji-core-foundation.607749f4.min.js:1)

    at CommonResponseParser._parseByStatus (fiji-core-framework.fb92133b.min.js:1)

    at CommonResponseParser.parse (fiji-core-framework.fb92133b.min.js:1)

    at ResponseParser.parse (fiji-core-framework.fb92133b.min.js:1)

    at NetworkClient.<anonymous> (fiji-core-framework.fb92133b.min.js:1)

    at step (fiji-core-framework.fb92133b.min.js:1)

    at Object.next (fiji-core-framework.fb92133b.min.js:1)

    at fulfilled (fiji-core-framework.fb92133b.min.js:1)

...

VM11:1 POST https://sentry.io/api/1448026/store/?sentry_key=somekey&sentry_version=7 413 (Request Entity Too Large)

...

VM11:1 PUT https://api-ucc.ringcentral.com/restapi/v1.0/account/~/extension/~/meeting/xxxyyyzzzz 503 (Service Unavailable)

When looking at Network tab in devtools,

{

  "errorCode" : "AGW-105",

  "message" : "Internal Server Error. Consult RC Support.",

  "errors" : [ ]

}

POST to https://sentry.io/api/1448026/envelope/?sentry_key=somekey&sentry_version=7 gets an OK

The next POST to that URL throws 413 Request Entity Too Large.


This issue does not happen with RingCentral Video. Just RingCentral Meetings API is impacted.

We noticed this issue around 8 am CT and the issue was resolved 2 hours later around 10 am CT. https://status.ringcentral.com/ was showing no issues. It appears that RingCentral does not have adequate monitoring of their APIs. I don't know whether to believe https://status.ringcentral.com/ or not.

Just FYI, RingCentral support contacted us 30 minutes to inform us that the problem was fixed. The issue was fixed 5 hours ago; so they were late to the party. Not only that, they told us to uninstall and reinstall RC App for everyone having a problem. RingCentral support is not good.

@Mary-Community_Moderator could you please let RingCentral support managers and high-ups know that asking customers to uninstall and reinstall RC App really is not a good selling point when the error is clearly in your API?

Reply


Terms & ConditionsCookie settings