Odoo errors, solved by the community

Answered by OdooNetworkThis usually happens when a session was left open on another device, or the offline order queue got stuck. Check Point of Sale → Orders for orders still marked "unsynced," make sure only one active session is open per register, and if orders are still stuck, close the session, clear the browser cache for the POS tab, and reopen — queued orders sync automatically once the connection is confirmed stable.

Answered by OdooNetworkThis is almost always a user group/permissions issue rather than a bug. In Settings → Users, check the user's assigned groups under the Sales section — they may only have "User: Own Documents Only" access instead of the broader team-level access needed. Also confirm the record's sales team matches a team the user belongs to.

Answered by OdooNetworkMost often this means the compliance CSID (certificate) either wasn't fully onboarded or has expired. Go to your Accounting → ZATCA integration settings and re-run the onboarding/renewal flow. Double-check the OTP used during onboarding matched the correct ZATCA portal environment (sandbox vs. production) — mixing the two is a common cause.

Answered by OdooNetworkSlowdowns like this are typically caused by accumulated logs, old attachments, and unused draft records bloating the filestore and database. Archive old records you no longer need active, review Settings → Technical → Logging for excessive log retention, and consider a filestore cleanup pass. If it's a hosted instance, this is exactly the kind of thing managed hosting monitors proactively.

Answered by OdooNetworkFirst check that 'installable': True is set in the module's __manifest__.py. Then, with Developer Mode enabled, go to Apps → Update Apps List before searching for it again — Odoo won't pick up new modules on disk until the apps list is refreshed. If it still doesn't appear, check the Odoo server log for a traceback during load.