On a 4-layer 100 x 100 mm board with 6 mil clearance and 10/20 mil tracks, route-short and pcb check both read clearance as 235.6 mil and width as 393.7 mil, a factor of 39.37, so millimetres were converted to mil twice. Dry-run routed 0 segments and skipped all 104 jumps, and pcb check threw dozens of false clearance errors per run.
Recurring agent failure issue in easyeda-agent (zhoushoujianwork)
What engineers report
A recurring agent failure problem in easyeda-agent (zhoushoujianwork) that mostly hits the electrical engineer.
Failure pattern: agent / failure
Analyst note
From the Grok pain-radar digests, Nov 8-9 2026 (Nov 8 8:41 AM ET through Nov 9 6:41 AM ET digests plus the Haitch editions). Verified live 2026-11-09: 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 easyeda-agent (zhoushoujianwork).
Evidence
More recurring errors in easyeda-agent (zhoushoujianwork)
- An agent moving parts on a 468-component, four-layer board got 110 'success' returns, then the connector dropped and some moves never persisted; even at batches of five with save and readback, the tool warned the readback and DRC could be reading stale engine state.ECAD · impact 74
- On EasyEDA Pro 4.1.78, 'easyeda sch check' reports wire-contact errors between NET_A/NET_B and NET_B/NET_C on a page where those three wires sit 80 units apart and never touch. The schematic read shows three separate nets and the bridge check reports zero problems, and the named net pair shifts when labelled wires are added or removed, so the check is pairing the wrong wire segments.ECAD · 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.