kicad-cli from KiCad 10.0.6 opens a legacy KiCad 5 .sch, exits 0, and writes a netlist with no components and no nets, while 'kicad-cli sch upgrade' fails on the same files. netlist_audit, check_straps, the schematic side of check_bom_sync and pin_requirements all see an empty design and report nothing, without saying the design was empty. A whole class of older boards gets a green result from checks that never looked at them.
Silent failure reported against hive-pcb-flow (Hive-RSI-Lab)
What engineers report
A silent failure reported against hive-pcb-flow (Hive-RSI-Lab): reports success, or uses stale data, while the result is wrong or missing.
Recorded mode: agent / silent failure
Analyst note
From the Grok pain-radar digests, Nov 13-14 2026 (Nov 13 10:41 AM ET through Nov 14 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-14: 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 hive-pcb-flow (Hive-RSI-Lab).
Evidence
More recurring errors in hive-pcb-flow (Hive-RSI-Lab)
- A lesson written into the router agent's rules after a radar-detector rebuild: one spec in a replayed cleanup chain added a track and a later spec removed it by uuid, but track uuids change every run, so on a clean rebuild the removal matched nothing, route_edit.py treated that as a no-op, and the track stayed in and shorted a supply rail. DRC on the committed board was clean because that board had been built step by step, not replayed. New rules: rip by net, layer and endpoints, compare a rebuild against the committed board, and count a removal that finds nothing as a failure.Electronics & PCB · impact 74
- A list of code defects found across boards PCB-0010 to PCB-0021 that the team had only been working around in docs. SES import can drop connections while still reporting fr_completion 1.0, Freerouting ignores edge and hole clearances, the DFM gate passes with the BOM and assembly leg skipped, a blockquoted brief silently turns off a whole requirements check, and current checks charge each via the full net current. Twelve boards in, the team keeps a written list of where its own pipeline lies to them.Electronics & PCB · impact 74
- A PCB check flow flags missing paste on every board using KiCad's stock ThermalVias footprints. Those footprints carry a second pad on bottom copper, under mask, where the vias land, never meant to be soldered. The check counts it as an exposed pad. The reporter placed all 482 ThermalVias footprints from KiCad 10.0.6 alone on scratch boards and 417 got the false error. Library intent and checker intent disagree on what a pad is.Electronics & PCB · impact 74
- A PCB flow found KiCad's 0.25 mm copper-to-hole default silently standing in for the fab's value, and a hand-made stackup draft with stripline widths off by about 10%. The generated 6-layer stripline widths are 0.1841, 0.1616 and 0.1177 mm against a hand draft of 0.165, 0.1484 and 0.1085, and the fab's minimum via left a ring thinner than its own floor.Electronics & PCB · impact 74
- An agent PCB flow cannot instance one schematic sheet N times, so repeated channels get copied by hand and drift. On a hifi receiver the left and right amps were generated as separate files with their own ref ranges: only 25 of 44 parts pair up by ref suffix, 8 of those pairs have different footprints, and 17 and 19 parts have no counterpart at all.Electronics & PCB · impact 74
- KRT 0.19.0's writer moves every copper graphic with no net token to silkscreen, so pours can't short to a copper logo, but footprint copper never carries a net in the file, so it also took the bridge of a SolderJumper-3 Bridged12 boot strap. A later silkscreen clean-up deleted it and the strapped pin floated, while KiCad connectivity ignores footprint copper graphics and each net-tie pad has its own net, so DRC saw '0 unconnected, 0 shorts' with or without the bridge. Two boot straps on a 6-layer board lost their bridges and the green DRC meant nothing.Electronics & PCB · 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.