A user's design imports a multi-solid STEP of a KiCad board (181-182 solids) with a skip list. After upgrading from 0.30.1 to 0.40.1, the bare PCB body is gone, components float in space, kept parts are missing, and parts that were skipped show up again: 204 to 220 bodies against 193 before. No error on the import feature, so the damage is silent. The cause is that the skip list stores 82 positional indices, and the new importer returns the same solids in a different order. Any ECAD-to-MCAD handoff that keys on order instead of identity breaks like this.

Silent failure reported against solidcraft (tangency-labs)

solidcraft (tangency-labs)MechanicalSilent failureMedium confidence

What engineers report

A silent failure reported against solidcraft (tangency-labs): reports success, or uses stale data, while the result is wrong or missing.

Recorded mode: validation / silent failure

Analyst note

From the Grok pain-radar digests, Nov 13-14 2026 (Nov 13 10:41 AM ET through Nov 14 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-14: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to solidcraft (tangency-labs).

Evidence

  1. 1tangency-labs/solidcraft Issue #15565: 0.40.1: design saved by 0.30.1 opens with wrong bodies from a STEP import (positional skip list); one solid fails to importgithub.com

More recurring errors in solidcraft (tangency-labs)

See all 42 solidcraft (tangency-labs) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.