Onshape-Lunaparts-Coallition (1piemanpie) errors

14 recurring problems engineers report in Onshape-Lunaparts-Coallition (1piemanpie), ranked by impact.

#29 by errors trackedPLMMCAD

Recurring Onshape-Lunaparts-Coallition (1piemanpie) errors, by impact

  1. 1A team built its own Onshape panel to push parts and drawings into their LUNA Parts system. A team member noticed new drawings showed no part number or name. Onshape's title block fills from part properties, and the team leaves those empty because "the number lives in the part's name." Fix writes "<part number> - <name>" as a note line. PR #45 adds a Check drawings screen that warns when quantity, material or number changed after the drawing was made, so "the title block is out of date," and uploads PDF, DXF and STEP only for parts someone ticked OK.PLM · Agent failure · 1 report74
  2. 2A team built its own Onshape panel to push parts and drawings into their LUNA Parts system. A team member noticed new drawings showed no part number or name. Onshape's title block fills from part properties, and the team leaves those empty because "the number lives in the part's name." Fix writes "<part number> - <name>" as a note line. PR #45 adds a Check drawings screen that warns when quantity, material or number changed after the drawing was made, so "the title block is out of date," and uploads PDF, DXF and STEP only for parts someone ticked OK.PLM · Agent failure · 1 report74
  3. 3Onshape will not let anyone rename parts linked from another document, so this FRC team keeps part numbers in their LUNA parts system, keyed by an onshape tag written into the notes field. Part identity is split across two tools, held together by a text tag.PLM · Agent failure · 1 report74
  4. 4Parts linked from other documents cannot be renamed through the REST API because the source is read-only, so the team stores part numbers in browser localStorage and shows them in its panel.PLM · Agent failure · 1 report74
  5. 5The Onshape API spec lists geometry types in capitals, but real bodydetails responses use lowercase, so every face looked non-flat and no DXF was built, while mocks using capitals let tests pass.MCAD · Agent failure · 1 report74
  6. 6The Onshape-to-LUNA panel cached the part and assembly lists for the whole session. A user saw No material on 26LP-T002 though it had Aluminum 6061, and the fix reloads after 30 seconds, re-reads before CREATE PARTS, and folds parts whose names already exist in LUNA.PLM · Agent failure · 1 report74
  7. 7Follow-up to last hour's #45/#46. After the title fix, the drawing number box still showed "----" because it "seems to read the drawing tab's own Part number property, not the part's" (#52). #53 answers how a drawing fixed in Onshape gets back into LUNA. "Until now, the only way was to attach the file by hand in LUNA." It adds an UPDATE FILES button that uploads the next revision. A HISTORY tab was added in #50 and removed in #51 within 15 minutes. Neither #52 nor #53 was tested against real Onshape or LUNA.PLM · Agent failure · 1 report66
  8. 8Follow-up to last hour's #45/#46. After the title fix, the drawing number box still showed "----" because it "seems to read the drawing tab's own Part number property, not the part's" (#52). #53 answers how a drawing fixed in Onshape gets back into LUNA. "Until now, the only way was to attach the file by hand in LUNA." It adds an UPDATE FILES button that uploads the next revision. A HISTORY tab was added in #50 and removed in #51 within 15 minutes. Neither #52 nor #53 was tested against real Onshape or LUNA.PLM · Agent failure · 1 report66
  9. 9Follow-up to last hour's #45/#46. After the title fix, the drawing number box still showed "----" because it "seems to read the drawing tab's own Part number property, not the part's" (#52). #53 answers how a drawing fixed in Onshape gets back into LUNA. "Until now, the only way was to attach the file by hand in LUNA." It adds an UPDATE FILES button that uploads the next revision. A HISTORY tab was added in #50 and removed in #51 within 15 minutes. Neither #52 nor #53 was tested against real Onshape or LUNA.PLM · Agent failure · 1 report66
  10. 10Follow-up to last hour's #45/#46. After the title fix, the drawing number box still showed "----" because it "seems to read the drawing tab's own Part number property, not the part's" (#52). #53 answers how a drawing fixed in Onshape gets back into LUNA. "Until now, the only way was to attach the file by hand in LUNA." It adds an UPDATE FILES button that uploads the next revision. A HISTORY tab was added in #50 and removed in #51 within 15 minutes. Neither #52 nor #53 was tested against real Onshape or LUNA.PLM · Agent failure · 1 report66
  11. 11Follow-up to last hour's PR #40. The panel now asks for the document microversion once and reuses parts, materials, mass properties and face data until it changes, removes a hover picture that cost 2 calls, backs off export polling, and stops calling Onshape for 10 minutes after a 402. It adds a call counter. A FIRST robotics team is rationing CAD API calls by hand.MCAD · Agent failure · 1 report66
  12. 12The assembly list showed rows like Shaft x2 with no way to tell which part they were. The fix adds a picture on hover and finds the row when the part is clicked in 3D.MCAD · Agent failure · 1 report66
  13. 13The same Onshape panel now reads each part bounding box to guess the process and thickness. Before, 26LP-T003, an aluminum shaft, got CNC instead of the lathe, and assembly highlight uses an occurrence path format that is a best guess, logged so a user can confirm it.MCAD · Agent failure · 1 report66
  14. 14The team's parts panel got stuck on "Loading parts" with a 402. Onshape gives apps outside its App Store a yearly API call budget, 2,500 on Free and EDU plans per the linked Onshape docs, and the panel spent two calls per part on every open. The fix fetches on hover, caches for 12 hours, and cuts calls per Part Studio open from 28 to 8. Anyone building agents on top of CAD APIs hits this kind of quota.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure14

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