The Checks tab collects source parser, WireViz and Graphviz diagnostics. A successful compile means the engine could interpret the harness and generate its schematic and BOM. It does not verify electrical ratings, connector mating, mechanical fit or supplier availability.
Read the current state
| State | Meaning and next step |
|---|---|
| Loading engine | Browser runtime files are loading. Keep the page open and check the connection if loading fails. |
| Compiling / Updating harness | The source or images changed. Wait for the current result. |
| Up to date | The latest source and attachments compiled successfully. |
| Source has errors / Needs attention | Inspect Checks, correct the source or undo, then compile again. |
Errors block the current result. Warnings can accompany a successful compile, for example an unused declaration or a renderer warning. Check the WireViz preview when a warning may affect appearance.
Clicking a diagnostic opens the YAML panel. Available line numbers appear with parser errors, but some engine messages only identify a component, field or image. The editor does not automatically place the cursor on the reported line.
Why an old drawing is still visible
The editor retains its last successful drawing and BOM while you make an incomplete or invalid change. This lets you inspect the previous harness, but it is not proof that the current source works. The YAML status and stale indicator tell you whether the result is current.
Model-based connection controls and rendered exports wait for a valid current result. YAML download remains available, including when you want to keep an unfinished document. Old compile replies cannot replace a newer accepted source revision.
Common problems
A property change is refused
Typed connector and cable controls compile a candidate before applying it. They reject invalid quantities and changes that would alter existing resolved connections. Read the inline error. Update affected connections or lists first, then repeat the property edit.
A count based on explicit pin IDs is read-only in the compact control. Change the pins list under Advanced or in YAML. Shared anchors may require editing the common definition in the source editor rather than changing an inherited object visually.
An image is missing or rejected
Match image.src to the attached relative filename, including subfolders and capitalization. Reimporting YAML alone does not retain custom attachments from the previous document. Use Import folder with images or Add images.
A failed library artwork download can be retried by compiling again. For custom SVG, convert CSS stylesheets to presentation attributes and flatten external images. The diagnostic includes the failing asset name. Unreferenced malformed artwork is ignored by compilation, but attached files still count toward import limits. See image import rules.
A component is absent from Layers or the BOM
Check whether a connection set instantiates it. A declaration alone can remain an unused definition. For a standalone visible component, a singleton set such as - [X1] is sufficient. Generated template instances appear under their instance IDs rather than as independent source definitions.
Disconnect is unavailable
The editor could not safely match the rendered connection to one supported source lane. Use the Connection sets editor or full YAML for templates, loops, mating arrows, chains and ambiguous references. See connections.
The engine timed out or stopped
Each editor uses an isolated browser worker. Runtime loading has a 90-second watchdog; an executing compile has a 30-second limit. A timeout or worker failure stops that worker and returns an error rather than leaving the operation pending indefinitely. The next compile can start a fresh worker.
Download your YAML before refreshing. Try compiling again after a loading failure; if compilation repeatedly times out, simplify the harness or reduce image and expansion costs. The browser runtime is loaded from the site, while harness source and image processing stay in the browser.
What Checks does not establish
This is schematic validation, not an electrical rule checker or a manufacturing approval. The BOM is generated from your entered data; it is not an inventory, quote or purchasing system. Compare exported drawings with the required pinout and part drawings before using them downstream. See current limitations.