# Troubleshooting (common questions)

> Common stops in Probe and what they're caused by — an incomplete take that's hidden, an empty corpus, the MCP address and registry access.

_Source: E-Sharp (esharp.se) · Probe guide_


Common stops and what they're caused by.

## "My board doesn't appear after upload"

The take is probably **incomplete**. A take becomes visible only once it's complete — before layout: schematic + BOM + netlist; after layout: schematic + BOM + ODB++. If you uploaded an ODB++ before its schematic/BOM, the take is hidden until what's missing arrives (see [boards, takes and the design line](/en/probe/support/boards-takes-and-the-design-line)).

## "A datasheet is missing for a part"

An empty corpus for a part usually means **never fetched**, not "fetched and came back empty" — no enrichment is triggered for a part whose board has never been ingested. Form-walled or 404 datasheets you upload yourself (see [the datasheet corpus lifecycle](/en/probe/support/datasheet-corpus-lifecycle)).

## "My colleague's AI uploads to the wrong machine"

The MCP address points wrong. The public address must be the one **other machines** reach the server on — `localhost` makes the client point at its own computer (see [Probe on Windows](/en/probe/support/probe-on-windows)).

## "Image download is denied"

You aren't logged in to the private registry. Log in with a GitHub PAT that has `read:packages` (see [self-hosted with Docker](/en/probe/support/self-hosted-with-docker)).

## "I can't write/review"

You probably lack a **review seat**, or the licence is blocking writes (entitlement exhausted or overage). See [seats, licence and fleet](/en/probe/support/seats-licence-and-fleet).

---

Can't find the answer? [Open a ticket](/en/book-demo) — support is connected to your account manager.

*Probe is E-Sharp's design-review engine.*
