TeamCraft's CAD folder import writes quantity 1 on every BOM line, even when an Inventor assembly places a bolt four times. The reference scan records which files an assembly references and not how often, so the new graph view shows x1 everywhere. SOLIDWORKS, NX and STEP files carry instance counts the server already reads for previews, but the BOM import never used them, and Inventor .iam occurrence data is not decoded at all.

Recurring agent failure issue in TeamCraft (rudalabs)

TeamCraft (rudalabs)PDMAgent failureMedium confidence

What engineers report

A recurring agent failure problem in TeamCraft (rudalabs) 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 TeamCraft (rudalabs).

Evidence

  1. 1rudalabs/TeamCraft Issue #247: Imported assemblies: every BOM line gets quantity 1, so the graph shows ×1 for parts used several timesgithub.com

More recurring errors in TeamCraft (rudalabs)

See all 5 TeamCraft (rudalabs) 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.