What does this error mean?
When you add custom modules to an Odoo.sh branch, the build process automatically runs a series of checks, including installing demo data – sample records used to populate a fresh database for development and testing purposes. If any module fails to load its demo data, the build is marked as failed with the message “Failed to install demo data.”
This can be triggered by any installed module, including Odoo’s own built-in modules, and does not necessarily mean our connectors caused the problem.
Why doesn’t this error appear when your modules are not installed?
This is the most common question we get, and it’s a fair one.
Odoo.sh only runs the demo data installation step when custom modules are present in the branch. Without them, Odoo.sh uses a pre-built database snapshot where demo data is already in place – so this step is skipped entirely, and any issues in Odoo’s own demo data are never exposed.
In other words, adding our modules does not introduce the bug – it simply triggers a build step that reveals a pre-existing issue in Odoo’s own code.
How to check whether our modules caused it
Open install.log from the failed build and search for the phrase demo data failed. You will find a line like:
WARNING: Module <module_name> demo data failed to install, installed without demo data
The <module_name> tells you exactly which module’s demo data failed to load. If it is an Odoo built-in module – for example mail, account, or stock – our modules are not the cause.
A more detailed error description (traceback) will follow that line. Even if you are not a developer, you can scan the file paths in it. If none of them mention our modules (such as integration, integration_shopify, integration_magento2, etc.), the issue is entirely outside our code.
Real-world example: In Odoo 19.0, the built-in mail module triggers this error due to an internal conflict in Odoo’s own code. Our modules appear nowhere in the error.
Is it safe to ignore?
Yes, completely. Demo data exists only to populate a fresh database with sample records for development and testing. It is never used in production. A failure to load demo data does not affect:
How the modules work
Your real business data
Your production environment
What should you do?
If you have confirmed that the failing module is not one of ours, you can safely merge the branch and proceed with deployment. The “Failed” build status is misleading in this case – it reflects an issue in another module’s demo data, not a problem with our connectors.
If you are unsure or the error does reference our modules, please reach out to our support team and attach the install.log file from the build – we will take a look straight away.