Depending on union order and seam angle, a boolean drops a whole rod yet still reports OK with a clean check; with tubes, one order comes out 4592 mm3 too large and passes the check.

Silent failure reported against solidcore (tangency-labs)

solidcore (tangency-labs)MechanicalSilent failureMedium confidence

What engineers report

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

Recorded mode: agent / false success

Analyst note

From the Grok pain-radar digest, Oct 24-25 2026 (Oct 24 evening to Oct 25 morning slots). Verified live 2026-10-25: issue/PR read on GitHub; 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 solidcore (tangency-labs).

Evidence

  1. 1tangency-labs/solidcore Issue #868: SMLib boolean: joining a rod to an equal crossing rod on a trimmed cylinder silently drops it (ellipse lost at the seam)github.com

More recurring errors in solidcore (tangency-labs)

See all 3 solidcore (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.