With a per-via diameter omitted, the pipeline reported solved and routed straight across a fixed GND via land, a gap of -0.200 mm, even though the board states a 1 mm minimum. Native DRC catches it afterward, but the router read one field and ignored the board-level rule next to it.

Recurring agent failure issue in bus-lanes-solver (tscircuit)

bus-lanes-solver (tscircuit)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in bus-lanes-solver (tscircuit) that mostly hits the electrical engineer.

Failure pattern: agent / 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 bus-lanes-solver (tscircuit).

Evidence

  1. 1tscircuit/bus-lanes-solver PR #170: repro: fixed via with omitted diameter overlaps a signalgithub.com

More recurring errors in bus-lanes-solver (tscircuit)

See all 2 bus-lanes-solver (tscircuit) errors

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.