Skip to main content

Cloudbeds Integration Disconnected After User Deactivation

The Cloudbeds integration may disconnect if the connected Cloudbeds user is deactivated. Relink the integration in Cloudbeds under an active user, then disconnect and reconnect in Event Temple to restore syncing.

Updated this week

If your Cloudbeds integration becomes disconnected, it is often because the Cloudbeds user account originally used to connect the integration was deactivated or removed. When this happens, Event Temple loses authentication access and the connection must be re-established.


Symptoms

  • Cloudbeds integration shows as disconnected

  • Error message referencing connection or authentication failure (see screenshot below)

  • PMS sync stops unexpectedly

We have received the following error from your pms provider:

User who approved this connection is not active anymore

Please contact support to resolve this issue.


Root Cause

The integration was connected using a Cloudbeds user account that has since been deactivated. Once that user is removed on the Cloudbeds side, the authentication token becomes invalid and the connection drops.


Resolution Steps

  1. In Cloudbeds, relink the integration to Event Temple using an active Admin user account.

  2. In Event Temple, disconnect the Cloudbeds integration.

  3. Reconnect the integration in Event Temple.

  4. Confirm the connection is active and syncing as expected.


Best Practice: To prevent this from happening again, connect integrations using a dedicated Admin-level user that will not be deactivated.

Did this answer your question?