The Carbon ERP Onshape panel read part number, revision and the BOM's Item and Quantity columns by hard-coded labels, so a company whose BOM template relabels a column, or keeps part numbers in a custom property, had no way to point it there. This is a CAD-to-ERP handoff that breaks on each company's own conventions.

Recurring agent failure issue in carbon (crbnos)

carbon (crbnos)PDMAgent failureMedium confidence

What engineers report

A recurring agent failure problem in carbon (crbnos) that mostly hits the product manager.

Failure pattern: validation / failure

Analyst note

From the Grok pain-radar digests, Nov 10-11 2026 (Nov 10 8:41 AM ET through Nov 11 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-11: 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 carbon (crbnos).

Evidence

  1. 1crbnos/carbon PR #2020: feat(onshape): choose the property behind part number, revision and BOM columnsgithub.com

More recurring errors in carbon (crbnos)

See all 4 carbon (crbnos) 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.