The verify script documents expected component counts in comments. One said 8 parts while the placed rig had 9, because the lever was missing from the list. The comment is the only documentation of what the number means, and the next editor reconciles against it. The proposed fix is to count placements from the build scripts.
Recurring agent failure issue in harmonic-analyzer (pedropaulovc)
What engineers report
A recurring agent failure problem in harmonic-analyzer (pedropaulovc) that mostly hits the mechanical designer.
Failure pattern: validation / failure
Analyst note
From the Grok pain-radar digests, Nov 9-10 2026 (Nov 9 7:41 AM ET through Nov 10 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-10: 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 harmonic-analyzer (pedropaulovc).
Evidence
More recurring errors in harmonic-analyzer (pedropaulovc)
- A DFM review of release v48 found docs/machining-dfm.md says PM-30MV CNC for the repeat parts while inventory.toml lists the same mill as manual handwheels on all three axes. The guide gives the rocker arm as about 270 x 21 mm against 292 x 29 mm in the STL, a pivot shaft length that disagrees with the print, and 19 bushings that do not exist in the bundle.MCAD · impact 74
- A drawing job crashed SolidWorks. The watchdog caught it and the lifecycle library relaunched it without raising. The new instance came up on a Graphics Issue modal the recovery code does not dismiss. Recovery reported success, the seat was not usable, and every COM task on the machine, part, assembly, verify, export, drawing, is blocked until someone clicks the dialog.MCAD · impact 74
- An audit of 263 tight bands found 81 slack, worth about 15 hours per build, and 19 that feed no stack at all. Along the way it found two stacks checked separately against the same 0.254 mm budget that add up to about 0.270, and a spec that says plus/minus .13 mm while the drawing sheet prints plus/minus .05 mm.MCAD · impact 74
- Since #2101 their drawing guideline says purchased-part supplier dimensions print as untoleranced REF. The shared supplier helpers still put the catalogue tolerance band on the sheets, so a dowel printed as (Ø.1250 +.0003/+.0001). A blind machinist review flagged it as over-specification. The fix removes the band fields from dowels, washers and shims across the fleet. The policy lived in a doc and the behaviour lived in code, and only a reviewer reading the printed sheet connected them.MCAD · impact 74
- The base and top frame put matched diameter 1.004 sockets on an 8.820 in row spacing, while the inventory gives the mill 8.75 in of Y travel and 7.5 in of throat, so each face needs two clampings rotated 180 degrees on parts that must slide together by hand with .004 clearance. A sister issue, #2392, found assembly sheets calling for a 20.86 in reading, a digital angle gauge, a 5 to 6 in micrometer and feeler leaves, none of which are in inventory.MCAD · impact 74
- The MATERIAL cell links the generic SolidWorks library material instead of the part's Material Specification. An audit of one build found 58 of 111 drawings, 77 of 147 pages, printing something other than the specification. Two print the wrong alloy outright: the cone gear prints Brass where the spec is C67500 manganese bronze, and the knife mount prints Plain Carbon Steel where the spec is O1 tool steel at 58-60 HRC. Another 18 never print their grade, and 29 purchased parts print a generic material.MCAD · impact 74
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.