Inspect a user connection in the dashboard

When an agent suddenly cannot reach a user’s Gmail, Calendar, or GitHub, the cause is almost always the state of that user’s connected account rather than your code. The dashboard shows that state directly, which is faster than adding logging and redeploying.

This guide covers only where to look. For what each state means, and the code that fixes it, follow the links to Troubleshoot connection errors.

Find the connection

Go to Dashboard > Connections and select the connection the agent uses — the name you pass as connection_name in your code, such as github-connect.

Each connection lists the connected accounts created against it. One row exists per user identifier you have authorized.

One account per user, per connection

A connected account is scoped to a single connection. A user who has authorized both Gmail and GitHub has two connected accounts, and they can be in different states.

Read the row

The row’s status is the diagnosis. Only ACTIVE accounts can serve tool calls; every other status names the exact step the user or your app still owes.

The dashboard reports the same value your code reads from account.status, so the row and the SDK never disagree. Use the dashboard for a one-off answer and the SDK when you need the check in code.

For the full status list and the fix for each one, see Start with diagnostics. For the webhook that pushes these changes to your app instead, see Detect when re-authentication is needed.

Narrow one user versus every user

The row count is the useful signal the SDK will not give you in a single call:

• One row is failing — that user needs to re-authorize. Send a fresh authorization link.
• Every row is failing — the connection is at fault, not the users. Open the connection’s own settings and confirm its credentials. A rotated or expired OAuth client on the provider side takes down every account beneath it at once.