Accuro API Issue Impacting Cloud Connect and OceanConnect Users [RESOLVED]

We have been receiving notifications that Cloud Connect and OceanConnect modules have been deauthorized from the Accuro API.  Requests to the Accuro API to refresh API access tokens are failing as the tokens expire.  This causes connected Cloud Connect and OceanConnect modules to stop synchronization of Ocean and Accuro.  It appears that this is related to scheduled maintenance on the Accuro API server that took place overnight.  We are working with QHR to determine the cause.

You may have received an email with the subject "Ocean Cloud Connect Deauthorized".  After receiving this email you must log into and re-authorize Cloud Connect. This process should take no longer than 5 minutes to complete. For a step-by-step guide on how to reauthorize your Cloud Connect configuration, please refer to this guide: Re-Authenticating Ocean Cloud Connect.

We apologize for any inconvenience this may cause, and we are working closely with the team at Accuro to ensure that maintenance activities do not disrupt Ocean connections in the future.

Update 2019-01-16: QHR has identified what they believe to be the issue and will be deploying a fix in the Accuro API release tonight.

Update 2019-01-17: This issue has been resolved in the Accuro API patch by QHR. We will continue to monitor for de-authorizations in the coming weeks to ensure the issue has been completely resolved.

Have more questions? Submit a request