app (CtrlZ-FRC4096) errors

5 recurring problems engineers report in app (CtrlZ-FRC4096), ranked by impact.

#86 by errors trackedMCADPDMPLM

Recurring app (CtrlZ-FRC4096) errors, by impact

  1. 1A FIRST robotics team tracks what to buy in a Slack List called "BOM List" in its build parts channel, with 38 items from April to October, 17 columns and 10 statuses. They're now building a Purchasing tab that copies it. PR #72 says it is "typed in by hand, separate from the BOM, which comes from Onshape." Open questions include whether Price is per item or per line, and the BOM README says costs are mentors-only while the Slack list shows prices to everyone. Linking items back to the BOM is step 5 of 6. Small team, same pattern as big ones.MCAD · Agent failure · 1 report74
  2. 2A FIRST robotics team tracks what to buy in a Slack List called "BOM List" in its build parts channel, with 38 items from April to October, 17 columns and 10 statuses. They're now building a Purchasing tab that copies it. PR #72 says it is "typed in by hand, separate from the BOM, which comes from Onshape." Open questions include whether Price is per item or per line, and the BOM README says costs are mentors-only while the Slack list shows prices to everyone. Linking items back to the BOM is step 5 of 6. Small team, same pattern as big ones.MCAD · Agent failure · 1 report74
  3. 3A robotics team's homegrown BOM tool crashes ("BOM stopped working") after every Onshape import, because newer Chrome returns a Promise from scrollIntoView and React then tries to call it as cleanup. The parts still save. The tests run in Node, so they never caught it.PDM · Agent failure · 1 report66
  4. 4An FRC team's app reads part numbers out of Onshape and guesses vendors by pattern, but a custom part named 'Spacer for am-1234' gets taken for bought, VEX is not in Purchasing's vendor list so it lands under Other, and manual fixes have to survive the next import. The patterns have not been checked against the team's real CAD.MCAD · Agent failure · 1 report66
  5. 5Writing part numbers into Onshape's Part number property only works in a workspace, not a version, breaking the one-part-number-everywhere plan.PLM · Agent failure · 1 report66

How it fails

  1. Agent failure5

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.