← Back to Index
control-kit (ZOGWORK)MCADConfidence: Medium

A robotics parts tool's Onshape BOM scan crashed on two instances whose linked source Onshape could not resolve, then told the user "Could not reach Onshape", which was false; the network was fine.

Impact Analysis

Persona
Mechanical Designer
Team Size Impact
5x Multiplier
Prototype Delay
3 Days
Est. Annual Cost
$30,000
  • 1 user · 1 month240 min
  • Rest of team960 min
  • Rest of year13,200 min

monthly_minutes × 12 × team_multiplier ÷ 60 × $75/hr = $30k/yr

$75/hr assumed rate.

Annual team-minutes decomposed from the reported monthly inputs.

Evidence & Sources

1 Sources
ZOGWORK/control-kit PR #42: Fix the scan crash on instances Onshape cannot resolve
github.com
→

Analyst Notes

From the Grok pain-radar digest, Oct 25-26 2026 (Oct 25 daytime to Oct 26 morning slots). Verified live 2026-10-26: issue/PR read on GitHub; title and state confirmed.