Connection Statuses
Every connection to a data source in LightLead has a status that reflects its health and authorization state.
All statuses
| Status | Display | Description |
|---|---|---|
Connected | Connected | The connection is active and working |
Reauthorization required | Reauthorization required | The token has expired and can't be refreshed automatically |
Missing permissions | Missing permissions | The authorized user lacks the required permissions |
Expired | Expired | The token has expired and automatic refresh is not possible |
Disconnected | Disconnected | The connection was disconnected by the user or the system |
In use | In use | The connection is actively being used by a running report |
Detailed description
Connected
The normal working state. The access token is valid, permissions are sufficient, and the source's API is responding.
- Data syncs on schedule
- Manual report runs are available
- In the UI: a green "Connected" indicator
How it's reached:
- A successful OAuth authorization
- Automatic token refresh via a refresh token
Reauthorization required
The access token has expired, and the refresh token is also invalid. Automatic refresh is not possible.
Causes:
- The user revoked access on the source's side
- The refresh token has expired
- The account password changed at the source
- The provider revoked the token for security reasons
Solution:
- Click "Reconnect" and go through OAuth again
- In the UI: a yellow "Reauthorization required" indicator
Missing permissions
The token is valid, but the authorized user doesn't have sufficient rights to access the data.
Causes:
- The user's permissions were downgraded in the ad account
- Access policies changed at the source
- The account was suspended or blocked
Solution:
- Check the user's permissions at the source
- Authorize with an account that has administrator rights
- In the UI: an orange "Missing permissions" indicator
Expired
The token has expired. This differs from Reauthorization required in that the refresh token is also expired.
Solution:
- A full reauthorization via OAuth
- In the UI: a red "Expired" indicator
Disconnected
The connection was disconnected — either manually by the user or by the system.
Causes:
- The user clicked "Disconnect"
- The workspace administrator disabled the connection
- Automatic disconnection after a prolonged Expired state (more than 30 days)
Solution:
- Click "Connect" to reauthorize
- In the UI: a gray "Disconnected" indicator
In use
The connection is actively in use — a report is running against it right now.
- Disconnecting is not possible until the report finishes
- Reauthorizing while a report is running may cause the report to fail
- In the UI: a blue "In use" indicator
Status transitions
Connected ──token expired──→ Reauthorization required
Connected ──permissions revoked──→ Missing permissions
Reauthorization required ──reconnected──→ Connected
Reauthorization required ──30 days without action──→ Disconnected
Missing permissions ──permissions restored──→ Connected
Missing permissions ──disconnected──→ Disconnected
Connected ──manually disconnected──→ Disconnected
Disconnected ──connected──→ Connected (via OAuth)
Connected ──refresh_token expired──→ Expired
Expired ──reauthorized──→ ConnectedImpact on reports
When a report runs, the statuses of all its connections are checked:
- All
Connected→ the report runs normally - Some
Reauthorization requiredorExpired→ the problematic sources are skipped, statuspartial - Some
Missing permissions→ skipped, statuspartial - All problematic → status
failed