FloConnectorDocs

Common issues

Most problems come down to one of a few things: the client has not reloaded the tool list, a connection has dropped, or a vendor is throttling. Here is how to clear each one.

Tools do not appear in Claude

The client connected, but no tools show up.

  1. Disconnect the connector in your client and reconnect it once. Clients cache the tool list, and a reconnect forces a fresh load.
  2. Check in the dashboard that the connection behind the profile still shows as connected.
  3. Check that you are an assigned member of the profile. Access is per person, so being an admin is not enough on its own. See Assign members.

A desktop client stays on "Connect"

Some desktop clients can stay on the Connect button even after you have signed in successfully, and only load the tools after a manual reconnect. This is a client-side lag in syncing the auth state, not something FloConnector can change from its end. Disconnect and reconnect the connector once and the tools load. The web client and Claude Code are not affected.

A connection shows as disconnected

A connection drops when the vendor's authorisation is revoked or expires and cannot be refreshed (for example the account was disconnected at the vendor, or a password change invalidated it).

  • Open the connector in the dashboard and reconnect it. You go through the same short OAuth handoff as the first time.
  • Any profile that pins the connection starts working again as soon as it is back to connected.

A profile shows no tools

  • Confirm the profile still pins at least one connected connection.
  • Confirm the tool set has not been trimmed down to nothing. See Create a profile.

Things are slow or a call reports throttling

If a vendor is rate-limiting your account, a tool reports it in its result and asks you to retry shortly rather than hammering the API. Wait for the hint and try again. FloConnector also paces tool calls per profile for fair use (60 a minute by default), which surfaces the same way. Either way the fix is the same: let the client wait and retry. See Rate limits for how the pacing works.

Still stuck?

Email support@floconnector.com with the workspace, the connector, and what you tried. The more specific, the faster we can help.