A pocket operation sometimes drops its final depth pass, producing 3 Z layers instead of 4.
Silent failure reported against FreeCAD (FreeCAD)
What engineers report
A silent failure reported against FreeCAD (FreeCAD): reports success, or uses stale data, while the result is wrong or missing.
Recorded mode: validation / dropped pass
Analyst note
From the Grok pain-radar digests, Oct 26-27 2026 (Oct 26 12:41 PM ET through Oct 27 7:41 AM ET digests plus the Haitch editions). Verified live 2026-10-27: issue/PR/thread 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
Evidence
More recurring errors in FreeCAD (FreeCAD)
- FreeCAD STEP import does not recognize identical objects.Mechanical · impact 82
- A FreeCAD CAM deburr operation looks successful but only deburrs a small segment of a 51.6 mm B-spline edge, saving one short G3 move, because a point-coincidence check fails against a tolerance tighter than the job's 0.01 mm.Mechanical · impact 74
- FreeCAD writes raw non-ASCII characters into AP214 STEP files instead of the spec-required escaped form, so a part named in Korean or Japanese or with pi opens in FreeCAD but is refused or shows broken names in several commercial CAD tools.Mechanical · impact 74
- The machine editor and docstrings say a rotary axis parent is the axis it is mounted on, but the rotation math and factory templates read it the other way round. On a B/C head whose C carries B, any work plane that needed C failed to solve, the post refused it, and the simulator turned the part instead of the head.Mechanical · impact 74
- Through the Python API the pattern is valid and Up-to-date, but the Body's shape doesn't include it, and the next feature lands before it. GUI users are fine. Scripts and macros get bodies without the mirrored geometry, so exports and mass come out wrong.Mechanical · impact 74
- When a script or macro passes a face from an earlier feature, the new Thickness becomes the Tip but bases itself on that earlier feature. Everything between silently drops out of the Body shape, and the new feature still shows Up-to-date with no error. The reporter calls it easy to miss, and it hits exactly the path agents use (Python, face names captured before later edits).Mechanical · impact 74
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.