Troubleshooting

Switch workspaces from the menu next to your name at the bottom of the sidebar. If a workspace you expect is missing, you may have been invited under a different email than the one you signed in with.

See Connect Claude and other agents over MCP: some terminals cannot open a browser on their own, so copy the printed link and open it yourself.

Open the app again; it lands on the sign-in page instead of reloading. If it does not, close and reopen it once.

LopeBase has not read that number yet, or the connection behind it cannot report it at all, which is different from a connection that is failing. Open the connection to see which.

Pages read from numbers LopeBase already has, not live on every page load, so there is always a short lag. The "Updated" note under a page's numbers says how old they are, and a Refresh button asks for a fresh read right now.

See Fix a connection that needs reconnecting.

Each one counts differently (cookies, bots, single-page apps). LopeBase shows each source separately rather than blending them, so pick one as your source of truth per property.

A single failed check is tried again before it counts as down, and a check against a vendor's status page or a shared endpoint can misfire. If your adapter's service checks use your own app's credentials, as the setup guide walks through, this is rare; mark a non-critical service as such so its failure shows as degraded instead of taking down the whole product.

Site-down alerts fire right away on purpose. A connected tool that stops answering waits about an hour of continuous failure before it alerts, so a short blip does not page you; it still shows on Overview sooner than that.

That is the point of marking it non-critical: its failure is visible without reporting your whole product as down. Uptime still shows it under Needs attention.

Check Settings, Alerts says the state for this browser. If notifications are blocked, allow them in your browser's site settings next to the address bar, then reload. Send yourself a test alert from the same page to confirm.

Confirm the Email checkbox is on in Settings, Alerts, and that email is enabled on your deployment; the page says if it is not.

Set "How serious" to Needs action in Settings, Alerts. That drops early warnings like a bounce rate approaching a limit, and keeps things that are actually broken or blocking.

See Plans, trial, and billing: it is most likely paused because your plan does not have room for every product you connected.

Check Billing for a past-due or suspended notice; new connections, operators, and dashboards pause until an unpaid invoice is settled.

You are most likely out of AI credits for the month. See AI reviews and credits for buying a pack or bringing your own key.

It expired, was revoked, or the admin who created it is no longer an admin of the workspace. Issue a fresh one from Connect Claude and other agents over MCP.

Create a new agent token with that scope (setup, read, or manage) from Settings, Agent access, and point the agent at it.

It looks for Claude Code, Codex, Gemini CLI, opencode, and Cursor Agent on your machine. If yours is not one of those, add the MCP server by hand; see Connect Claude and other agents over MCP.