Skip to main content
Start every debugging session with Usage. Open the logs to see exactly which integration was called, what action was attempted, and any error message returned. Most issues can be diagnosed in under a minute from the logs alone.

​
Start here

When something breaks, sort it into one of these buckets first:
  • Setup and pairing: install, browser approval, missing tools, stale sessions
  • Connections: reconnect flows, expired provider auth, missing permissions
  • Execution: the agent called a tool but the result failed or never returned
  • Routing: the right bot is online, but the wrong session or channel is receiving traffic

​
Common fixes

A Needs reconnect status usually means the provider credential expired, was revoked, or needs fresh consent.Go to Connections, expand the row, and run Reconnect. Then retry the same task from your agent.
Open Usage and inspect the failed request first. The log tells you which integration ran, which action was attempted, and whether the problem is likely connection-related or provider-side.Common causes include invalid parameters, expired auth, missing scopes, or a temporary provider outage.
Rate limit errors usually come from the provider, not ClawLink. ClawLink retries transient failures automatically, but repeated bursts can still fail if the provider account limit is too low for the workflow.Slow down the workflow or reduce how often the agent triggers that provider.
Some integrations—including Gmail, Google Sheets, and Google Calendar—use OAuth tokens that expire over time. When a token expires, the integration will stop working until you refresh it.To fix this:
1

Go to Dashboard > Connections

Open your dashboard and navigate to Connections.
2

Reconnect to get a fresh token

Expand the affected row and click Reconnect. This runs the hosted provider flow again and refreshes the token.
Manual key entry is a fallback path. If it fails, the simplest fix is usually to switch back to browser pairing.Check the following:
  • Make sure the key starts with cllk_live_...
  • Confirm you copied the raw key when it was first shown after creation
  • Revoke old keys you no longer trust and create a fresh one if needed
  • If possible, remove the manual key and run browser pairing instead

​
Deep-dive articles

For narrower client-side issues (OpenClaw gateway behavior, session routing, token usage), see the official OpenClaw documentation. For anything between your agent and ClawLink — connections, pairing, execution failures — start in Usage and work through the common fixes above.