Updates and troubleshooting

For the person who manages Cayamanan: make changes in a restored practice copy before changing the live system.

Before an update, read the release notes, back up the database and attached files, and test the same change on a restored copy. Keep the Cayamanan core revision, custom addons, Python dependencies, and PostgreSQL version recorded together. Update modules only after the new source and dependencies are in place.

When something fails, record the time, user, page, action, expected result, and exact message. Check the Cayamanan server log and browser console without posting passwords, tokens, customer data, or full database copies publicly. Try to reproduce the issue with the least data and note whether it also happens for an administrator.

Do not repeatedly restart or upgrade a production database without understanding the error. Restore the previous tested version when your documented rollback plan requires it. Version upgrades across major Odoo releases need a separate migration plan; a module update is not a database migration.