With two BoMs for one product, each tied to a different warehouse's manufacturing operation, switching a saved draft manufacturing order from BoM A to BoM B raises 'Record does not exist or has been deleted.' The reservation update still points at component moves the BoM switch already deleted.

Recurring agent failure issue in odoo (odoo)

odoo (odoo)PDMAgent failureMedium confidence

What engineers report

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

Failure pattern: validation / 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 odoo (odoo).

Evidence

  1. 1odoo/odoo PR #293521: [FIX] mrp: avoid MissingError when changing BoM of a saved MOgithub.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.