Odoo’s error messages are more helpful than most. The problem is that they use Odoo’s vocabulary, so they read as obstruction rather than explanation.<\/p>\n
Almost every one of them is protecting something. This article translates the common ones.<\/p>\n
What it usually says:<\/strong> something about the record being referenced elsewhere.<\/p>\n What it means:<\/strong> other records point at this one. Deleting it would leave them pointing at nothing.<\/p>\n A customer with invoices. A product with stock moves. A journal that has entries.<\/p>\n What to do:<\/strong> archive it instead.<\/strong> Archiving hides the record from normal views and keeps every link intact. It is almost always what you actually wanted.<\/p>\n A general rule:<\/strong> archive by default, delete almost never.<\/p>\n What it means:<\/strong> this product already has stock moves or order lines, and its unit is embedded in all of them. Changing it would make every historical record wrong.<\/p>\n What to do:<\/strong> in most cases, nothing \u2014 the change is not safe. Options:<\/p>\n Prevention is the real answer.<\/strong> Decide units of measure before importing products. This error is the most common expensive mistake in Odoo setups.<\/p>\n What it means:<\/strong> the invoice or journal entry has a sequence number and has hit your ledger.<\/p>\n What to do:<\/strong> issue a credit note<\/strong> to reverse it, then create a corrected version. Odoo has an option to reverse and open a new draft in one step.<\/p>\n Why:<\/strong> this is standard accounting practice, not an Odoo quirk. Any auditor expects exactly this trail.<\/p>\n FIGURE 1: FOUR ERRORS THAT ARE PROTECTING YOU<\/p>\n Cannot delete<\/p>\n Cannot change unit of measure<\/p>\n Cannot edit a posted entry<\/p>\n Cannot cancel a done transfer<\/p>\n What it means:<\/strong> you are trying to deliver more than is available at that location.<\/p>\n Check these, in order:<\/strong><\/p>\n Is stock at the right location?<\/strong> Very common. The goods exist, in a different warehouse or a sub-location the operation does not draw from.<\/p>\n Is it reserved for another order?<\/strong> Compare On Hand<\/strong> against Free to Use<\/strong>. The difference is committed to other customers.<\/p>\n Is the receipt recorded?<\/strong> Goods can be physically present and not yet validated in the system.<\/p>\n Is your stock record simply wrong?<\/strong> Run a count.<\/p>\n What to do:<\/strong> find which of the four it is before changing settings. Allowing negative stock to make the error go away hides a problem rather than fixing it.<\/p>\n What it means:<\/strong> a transaction needs an accounting account and the configuration does not say which one.<\/p>\n Usually one of:<\/strong><\/p>\n What to do:<\/strong> the message usually names the model. Go to that configuration and fill in the missing account. Ask your accountant which account<\/strong> \u2014 this is not a guess.<\/p>\n Prevention:<\/strong> this appears when a configuration was half-completed at setup. Running a full test cycle before go-live catches almost all of them.<\/p>\n What it means:<\/strong> the transfer is already Done. Stock moved and, with automatic valuation, value posted.<\/p>\n What to do:<\/strong> create a return<\/strong> \u2014 an opposite movement. Same principle as a credit note in accounting: you do not erase history, you post a correction.<\/p>\n What it means:<\/strong> your user does not have the rights.<\/p>\n Two possibilities, and they need different answers:<\/strong><\/p>\n You should have access and do not.<\/strong> Somebody needs to add you to the right group.<\/p>\n You should not have access.<\/strong> The restriction is working. Find out who does.<\/p>\n Do not solve this by making everyone an administrator.<\/strong> It is the most common and most damaging response to permission errors.<\/p>\n FIGURE 2: TWO WAYS TO RESPOND TO AN ERROR<\/p>\n Fixing the cause<\/p>\n Hiding the symptom<\/p>\n What it means:<\/strong> something points back at itself. A bill of materials containing itself. A partner set as its own parent. A category loop.<\/p>\n What to do:<\/strong> trace the chain until you find where it loops back. Usually a data entry mistake rather than a system problem.<\/p>\n Usually one of three:<\/p>\n A missing library on the server.<\/strong> PDF generation needs specific components installed. Common on self-hosted setups after a server change.<\/p>\n A template error<\/strong>, if the report has been customised.<\/p>\n Data the template did not expect<\/strong> \u2014 a missing value where the template assumes one exists.<\/p>\n What to do:<\/strong> try a different record. If it prints, the problem is data in the first record. If nothing prints, it is server-side and needs your technical partner.<\/p>\n Not an error message, and worth knowing what to do.<\/p>\n Check the browser console<\/strong> \u2014 press F12. There is often a message there that never reached the screen.<\/p>\n Try a different record.<\/strong> Isolates data from system.<\/p>\n Try a different browser.<\/strong> Rules out a cached asset.<\/p>\n Ask whether anything was installed or updated recently.<\/strong> A module or an upgrade is the usual cause.<\/p>\n Handle yourself: missing configuration, permission questions, stock discrepancies, anything with a clear message naming what is missing.<\/p>\n Escalate to your technical partner:<\/strong><\/p>\n FIGURE 3: WHAT TO SEND WHEN YOU ESCALATE<\/p>\n The exact message<\/p>\n What you were doing<\/p>\n What changed<\/p>\n Five habits.<\/p>\n Run a full test cycle before go-live.<\/strong> Sales, purchase, stock, invoice, payment. Most configuration errors surface here.<\/p>\n Decide units of measure early.<\/strong> The most expensive category to fix later.<\/p>\n Archive rather than delete.<\/strong> Avoids an entire class of errors.<\/p>\n Count receipts properly.<\/strong> Prevents most stock discrepancies.<\/p>\n Keep customisation in modules and test at upgrades.<\/strong> Prevents most post-upgrade errors.<\/p>\n Most Odoo errors are protections, and the message usually says what is missing.<\/p>\n Archive instead of deleting. Credit note instead of editing. Return instead of cancelling.<\/strong> Those three cover a large share of what people hit.<\/p>\n And when you escalate, send the exact message, what you were doing, and what changed recently<\/strong>. That third one is usually the answer.<\/p>\n Hitting an error you cannot get past?<\/p>\n Get in touch. Send us the exact message and what changed recently \u2014 that combination usually identifies it straight away.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":" Read the message Odoo’s error messages are more helpful than most. The problem is that they use Odoo’s vocabulary, so they read as obstruction rather than explanation. Almost every one of them is protecting something. This article translates the common ones. “You cannot delete this record” What it usually says: something about the record being […]<\/p>\n","protected":false},"author":3,"featured_media":9121,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[],"class_list":["post-9120","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-odoo"],"yoast_head":"\n“You cannot change the unit of measure”<\/h2>\n
\n
“You cannot edit a posted entry”<\/h2>\n
\n
\n
\n
\n
“Not enough stock” or “insufficient quantity”<\/h2>\n
“No journal found” \/ “No account configured”<\/h2>\n
\n
“You cannot cancel this transfer”<\/h2>\n
“This operation is not allowed” \/ permission errors<\/h2>\n
\n
\n
“Circular reference” \/ recursion errors<\/h2>\n
Reports that will not print<\/h2>\n
The blank page or spinning loader<\/h2>\n
When to escalate<\/h2>\n
\n
\n
\n
\n
Preventing most of them<\/h2>\n
The short version<\/h2>\n