CaseMaker posted a 25.3 mm freeing cut on a 0.9 mm PCB router bit whose flute length was blank. One path checks the stated flute length before giving a cutter the freeing contour, while the other path checks geometry only. When the picker chose a 25 mm flute bit for a 25.3 mm profile, the contour fell through to the 0.9 mm bit with flute length 0 in the record, and the program ran 1 h 51 min against 14 min 47 s on the right bit.
Recurring agent failure issue in CaseMaker (SlyWombat)
What engineers report
A recurring agent failure problem in CaseMaker (SlyWombat) that mostly hits the mechanical designer.
Failure pattern: validation / geometry
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 CaseMaker (SlyWombat).
Evidence
More recurring errors in CaseMaker (SlyWombat)
- The CLI posted a 27-hour rotary CNC program that the app Save gate would have refused, and said nothing: the refusal lives in the app store and engrave.ts posts files directly and never consults it, so a headless run and the app disagree about what may leave the building, silently. A second bug in the same receipt has an oversize warning claiming Generate refuses a part before building the toolpath when it did not.MCAD · impact 74
- The maintainer wants the elephant and panther demo parts passing before any bench work. The elephant mesh in a hardwood blank stops at "no candidate cutter plan." The stand-in reaches 32 percent of the surface from the top, proposes six setups for 80 percent, and one program runs about 18.5 hours. The gate is the simulation, and it isn't there yet.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.