Read the boundary result
| Result | Interpretation | Next action |
|---|---|---|
| One or more exposed boundaries | At least one checked edge has no adjacent face under this method. | Inspect whether the affected surface was intended to be closed. |
| Zero exposed boundaries | No boundary was detected in the supported completed check. | Review other findings and intended parts; do not infer that all topology is valid. |
| Failed or unsupported input | This operation has no completed boundary result. | Return to the producing application or a supported export. |
The server checks each supported placed build item independently after unit conversion and component/build transforms, then aggregates counts. It matches exact endpoint coordinates, with no distance-tolerance welding. Invalid-coordinate and degenerate triangles are excluded from edge incidence; duplicate triangles remain included. Components connect at shared vertex coordinates. No spatial intersection screen runs here.
A legitimate repeated build item is different from a repeated triangle inside one mesh resource. A package may contain several closed parts. Neither their quantity nor zero exposed boundaries establishes that their placement or intersections are acceptable. Volume availability has separate validity gates; unavailable volume is not another failed boundary test.
Expected boundary arithmetic for repeated placements
A cube missing one square face has four boundary edges. Placing two separate copies gives eight under independent per-item checking; it does not repair the resource. This is expected mathematics, not an observation from the production endpoint or a physical print.
Use the 3MF closure guide to interpret the boundary and the edge-sharing check for topology questions.