A support generator's Onshape feature is a hand port of its engine, and it fell behind. Rib tines in the Onshape version ran 0.5 mm into the part and side-fin tines 0.30 mm, while the web engine had stopped tines at the surface since an earlier change. The fix adds a test that reads every engine number the FeatureScript copies and compares it with the engine, and it fails on main.
Recurring agent failure issue in support-fins (gittrahan)
What engineers report
A recurring agent failure problem in support-fins (gittrahan) that mostly hits the mechanical designer.
Failure pattern: validation / failure
Analyst note
From the Grok pain-radar digests, Nov 10-11 2026 (Nov 10 8:41 AM ET through Nov 11 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-11: 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 support-fins (gittrahan).
Evidence
More recurring errors in support-fins (gittrahan)
- Support walls were only checked with probes inside the part, so in a recessed box the last probe landed on the end wall's face outside the part, passed, and the wall was built flush against the end wall where it welds (30 support vertices at 0 mm).MCAD · impact 74
- 3MF project analysis flattened component meshes and lost which part and face each triangle came from, so independently configured parts could not be rebuilt after a subtraction.MCAD · impact 66
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.