# Fix a connection that needs reconnecting

> What the Needs reconnecting state means, why LopeBase waits before showing it, and how to fix a revoked key, expired sign-in, or rate limit.

Source: https://lopebase.com/docs/reconnect-a-connection
Updated: 2026-10-08
Open in the app: https://app.lopebase.com/connections

A connection can stop working for a few different reasons: a key got revoked, a sign-in expired, or the service is just busy for a moment. LopeBase tells these apart so a brief hiccup never looks like a broken connection, and only asks you to act when something really needs it.

## What the different states mean

| What you see | What it means |
| --- | --- |
| Needs reconnecting | LopeBase confirmed the key or sign-in no longer works, by checking it directly, not from one failed read. Your stored numbers stay on screen, marked with when they last refreshed. |
| Limiting requests | The service asked LopeBase to slow down. Numbers fill back in on their own within a few minutes; nothing to do. |
| Did not answer | A one-off timeout or network hiccup. This usually clears itself on the next check. |
| Failing | Something else went wrong reading this connection. Try again in a few minutes; if it continues, it is worth a look. |

Only "Needs reconnecting" needs you to do something. LopeBase checks a connection's credentials directly before showing this state, so a service that briefly turns away a good key does not get flagged by mistake.

## Fix it

1. **Find the connection:** Open Connections, or follow the Reconnect link next to the numbers on the page where you noticed it, or in the bell at the top of the sidebar. [Open Connections](https://app.lopebase.com/connections)
2. **Reconnect it:** For a connection that signs in (Google, GitHub, Cloudflare, Bing), press its Connect button again and approve the sign-in. For one that uses a pasted key, open it and paste a fresh key from the service.
3. **Confirm it worked:** LopeBase tests the new key or sign-in immediately. If it works, the connection clears and its numbers start catching up. Reconnecting one sign-in clears the "needs reconnecting" flag for every other connection using that same sign-in too.

## Why a key stops working

The most common reasons, by kind of connection:

- **OAuth sign-ins** (Google, GitHub, Cloudflare, Bing): the access you approved was removed on the service's side, or your account there lost permission to the project or site.
- **Pasted API keys** (PostHog, Sentry, and others that take a key): the key was deleted or rotated on that service.
- **The LopeBase Adapter**: its signing secret changed in your app's environment without updating it here, or the adapter was removed from a deploy.

## Where to go next

- [Connect your tools](https://lopebase.com/docs/connections) for how each kind of connection is set up.
- [Troubleshooting](https://lopebase.com/docs/troubleshooting) for other problems, like numbers that look missing or stale.

## If something goes wrong

### I reconnected it but it still says needs reconnecting

Give it a minute; LopeBase tests the new key before clearing the flag. If it still shows after that, the new key likely does not have the access this connection needs, such as read access to the right project.

### A connection keeps needing reconnecting every few days

That usually means the key or token the service issued is short-lived by design. Check whether that service offers a key that does not expire, or reconnect the OAuth sign-in instead of a pasted key where that option exists.

### My numbers look stale but nothing says needs reconnecting

A connection can be slow to refresh without being broken. Check [Troubleshooting](https://lopebase.com/docs/troubleshooting) for numbers that are missing or look wrong.

### Do I lose history while a connection needs reconnecting

No. Nothing is deleted. The last good numbers stay on screen, marked with when they were last refreshed, until the connection is fixed.