> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot a GoHighLevel connection

> Use the connection check to distinguish authorization problems from temporary provider failures.

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.

| Status | Next step |
| - | - |
| Connected | The location check succeeded; retry the actual feature that failed |
| Connection not checked | Open the popover to start the check |
| Checking connection... | Wait for the location check to finish |
| Refreshing token... | Wait for refresh and its follow-up connection check |
| Couldn't check the connection. Close and reopen to try again. | Close and reopen the popover to retry this failed check |
| Not connected | Use **Accounts → New account → Connect GoHighLevel** in the owning workspace and authorize the location |
| Token expired | Use **Refresh from Agency** if the location belongs to the connected agency; otherwise reconnect the location |
| Access revoked | Reauthorize the correct location in GHL |
| Connection misconfigured | Contact support with the account ID, location ID and error; repeating authorization may not fix a location mismatch |
| Couldn't reach GoHighLevel | Retry later; this can be a network or provider failure |

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](/v3/guides/ghl/connect), [calendar debugging](/v3/guides/troubleshooting/booking), and [chat response settings](/v3/guides/troubleshooting/chat-replies).

**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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.