For surface-only STEP models the pipeline wrote surface area into geometric_metadata.volume, and loose faces next to solids were added into the solid volume, so a 10 mm cube plus a stray face came out at 1171.43 instead of 1000. Downstream asset metadata looked plausible and was wrong.

Recurring agent failure issue in visual-asset-management-system (awslabs)

visual-asset-management-system (awslabs)MCADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in visual-asset-management-system (awslabs) that mostly hits the mechanical designer.

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 visual-asset-management-system (awslabs).

Evidence

  1. 1awslabs/visual-asset-management-system PR #1247: fix(pipelines): report no volume for a STEP model with no solid in CAD/Mesh Metadata Extraction (#1190)github.com

More recurring errors in visual-asset-management-system (awslabs)

See all 2 visual-asset-management-system (awslabs) 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.