Exported AASX packages were non-conformant when a supplementary file had upper-case letters in its name: the file was stored under its real name but the relationship pointed at a lower-cased one, and the conformance tests flagged 'Relationship has non-existing target'. The fix was merged into a branch after that branch had already been squash-merged, so it never shipped, then it conflicted with another writer change, and taking either side alone broke the other.

Recurring agent failure issue in idta-submodel-editor (hadijannat)

idta-submodel-editor (hadijannat)PDMAgent failureMedium confidence

What engineers report

A recurring agent failure problem in idta-submodel-editor (hadijannat) 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 idta-submodel-editor (hadijannat).

Evidence

  1. 1hadijannat/idta-submodel-editor PR #391: Reference supplementary files by their stored part names in exported AASX packagesgithub.com

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.