control-kit (ZOGWORK) errors
5 recurring problems engineers report in control-kit (ZOGWORK), ranked by impact.
#92 by errors trackedPLMMCAD
Recurring control-kit (ZOGWORK) errors, by impact
- 1An Onshape-to-purchasing tool ordered 30 screws where the assembly needed 120 because it took the largest quantity per SKU per Part Studio; eight SHCS next to a motor were silently folded into a kit and vanished, and a team part was priced as a vendor product.PLM · Agent failure · 1 report74
- 2A live scan of an FTC team's Onshape model counted 32 Expansion Hubs ($8,800) because every body of one imported model matched the REV SKU, and a "sold individually" rule priced the $229.50 bundle once per CAD piece ($918).MCAD · Agent failure · 1 report66
- 3A 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.MCAD · Agent failure · 1 report66
- 4In the Onshape BOM review panel, 'Use AI suggestion' could overwrite a part decision the engineer had already made by hand, and a scan stream ending without a result reset silently.PLM · Agent failure · 1 report66
- 5Onshape's v9 API has no translation that picks a face, so to get a DXF for a flat part they read bodydetails geometry and draw the face themselves, at one or two billable requests per part.MCAD · Agent failure · 1 report66
How it fails
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.