Skip to main content
Start inside the affected client account. A workspace connection, stored token, or visible account row does not prove that this location can still be reached.

​
Run the check

  1. Open Sub-account connection in the portal header.
  2. Wait for the current result; the check makes a request to GHL for this account’s location.
  3. Follow the displayed status below, then reopen the check.
  4. When it reports Connected, retry the original operation, such as loading calendars or sending a test reply.
The connection checker attempts token refresh after an unauthorized provider response. A refresh success message is followed by a new connection check; use that result before retrying the workflow.

​
If only one feature fails

A successful location check confirms access to that location, not every permission or configuration. For booking, check the assistant’s assigned calendar and tool result. For chat, inspect the selected contact, active tag and delivery error. Include the time, affected account/location, failed operation and displayed error when contacting support. Do not send API keys, access tokens or client secrets. Customers do not need to edit the application’s OAuth redirect URL to follow this recovery process. See connect GHL, calendar debugging, and chat response settings. Refresh from Agency is unavailable while a check or refresh is running. It uses the account’s owning agency connection; choosing it does not switch the account to another location. A token-refresh success message is not the final result—wait for the new Connected check.