# Troubleshooting

What your assistant's model sees, and fixes for the problems you are most likely to meet.

## What your assistant sees

The server works on the projects stored in your Crossprobe account, and reads them there. Your assistant's model sees what the tools return when it asks: for example a part's pins, a net, a list of check results, or a picture of the board. It never gets your files as a whole. Where that model runs is up to your assistant and its settings. See [Privacy and data](https://crossprobe.ai/docs/reference/privacy-and-data/).

## Troubleshooting

For the local server, see [its own page](https://crossprobe.ai/docs/mcp/local/#if-something-doesn-t-work).

### Building a board

- **"Nothing was built", with a list of problems.** The spec names a symbol, pin or footprint the libraries don't have, or a symbol with pins its footprint has no pads for. The list says which; the assistant corrects the spec and builds again. This does not count as a build.
- **The report isn't clean.** It lists what is left: unrouted connections, DRC results, parts that found no room. Ask the assistant to make the board larger or use four layers, or to say where a part belongs ("put J2 next to J1"). `footprintWarnings` are warnings inside a library footprint itself and don't count.
- **"That position is taken".** A part was moved onto another. Ask the assistant to look at the picture and pick a free spot.
- **A part is far from where it belongs.** Say so: "put the diode next to the fuse", "the connector at the left end of the bottom edge". See [what you can say about the layout](https://crossprobe.ai/docs/mcp/build-a-board/#what-you-can-say-about-the-layout).

### Connecting and saving

- **"Today's board build is used".** An account without a plan gets one build a day; it counts again from 00:00 UTC. What was built can still be looked at and saved. See [what it costs](https://crossprobe.ai/docs/mcp/#what-it-costs).
- **The assistant can't connect, or gets "401".** If it signs in by itself, ask it to connect again (in Claude Code: `/mcp`, then the server) and sign in when the browser opens; it may have been disconnected under **Connect an assistant…** in the account menu. With an access token, the token is wrong, revoked, or was copied without its `cp_` start: make a new one there.

- **"Too many requests without a valid access token" (429).** Several attempts from your address had no valid token, and the address is turned away for a few minutes. Fix the token and try again later.
- **A build was stopped after 150 seconds.** The board is too large or too dense for the time allowed. Fewer parts on the sheet, a larger board or four layers make it quicker.
- **I don't see what the assistant made.** Ask it whether it saved: an unsaved proposal doesn't show in the app. Then open the project from the project menu (**Open from your account**), or with the link the assistant gave you.
