Troubleshooting

What you saw, and what to do about it.

Find the message or behavior below and read straight to the fix. Nothing here is a bug report form — every entry is something SoloSearcher does on purpose, even when it reads like a wall.

“AI prompts are locked until a Buyer Profile exists” #

Every skill needs a “who's buying” half before it can reason about a company, and your AI hit one before that existed. This is the exact message it saw:

Fill in the two-minute profile once and every skill unlocks. See Buyer Profile for exactly what's required and why it comes first.

A skill card says “Ready — gaps” or “Needs inputs” #

This is readiness, not an error — each skill declares what it needs on the company record before it can answer well, and the card reflects what's actually on file today. A card reads “Ready” when everything the skill needs is already on file, “Ready — gaps” when it can run but names what's missing so you know how much to trust the answer, and “Needs inputs” when there's nothing to run on yet. How many skills fall into that last state shows up as the locked count on the AI tab.

Add what the card asks for — a financial period, a document, a field on the record — and the state updates on its own. See Skills for the full arc from cold company to diligence.

My AI says the tool doesn't exist #

This is scope, not a bug. A read-only connection is never offered write tools in the first place — they're not on the list your AI can see, so if you ask for one it reports that the tool doesn't exist rather than being refused.

If you expect to be able to do something and can't, reconnect with read-and-write access, or use an API key granted the capability you need. See Tool reference for what each access level unlocks, and your Connections page in the app to grant it.

“Unauthorized” / 401 #

Your key is revoked, expired, or was copied incompletely. Keys begin smb_live_ and are shown exactly once, at creation — there's no way to re-display one to check it against what you pasted.

Don't retry-guess. Revoke the key and issue a new one in API keys & access, then copy it in full the moment it's shown.

“Too many failed authentication attempts” #

Ten failed sign-in attempts inside a rolling fifteen-minute window trip this — a lockout on the failure rate itself, separate from any single key being wrong. It clears on its own as old attempts age out of the window; there's nothing to reset by hand.

Wait it out, then paste your key carefully once rather than retrying repeatedly — each additional failure re-arms the window.

“Rate limit exceeded” #

Your connection asked for more than its budget allows in the window — the message names which one and how long to wait (“Rate limit exceeded for company_detail_reads. Retry in 37s.”, for example). These are cost bounds, not a penalty: see Limits for the budgets an agent most often hits and how the windows actually reset.

Nothing is lost when this fires — the call simply didn't run. Your AI usually resumes on its own once the window has room again.

“Monthly load cap reached (5,000/5,000…)” #

You've loaded 5,000 rows from the shared company universe this calendar month, which is the ceiling. Nothing you've already loaded is affected — every company already on your workspace stays exactly where it is; this only blocks loading additional rows until the budget renews. See Limits for what resets it and when.

Connection shows “Not connected yet” #

The browser approval step didn't finish. Open the connector again and sign in — approval is complete once SoloSearcher appears with its tools listed. See Connect Claude for the walkthrough, screenshot included.

ChatGPT couldn't authenticate #

Expected today, not a misconfiguration on your side. SoloSearcher gates which hosts may receive an authorization code, and ChatGPT's in-app sign-in isn't on that list yet — the connection refuses the registration and ChatGPT reports it couldn't authenticate. Use the Responses API route instead; see Connect ChatGPT for exactly where it stops and what works today.