Troubleshoot data synchronization in Hostinger AI Builder agentic mode by republishing your project when database fields are missing from live data. Publishing updates the live data structure to match Test data. Publishing also copies new Test data records to Live data. Data structure changes you make in the editor stay in Test data until you publish.
Understand the Two-Bucket data model
Hostinger AI Builder syncs data from Test data to Live data only when you publish, and never in the other direction:
- The Separate Bucket Concept: Think of the test and live environments as two iron buckets with the same shape. Publishing reshapes the live bucket to match the test bucket and adds any new items from the test bucket. Publishing never removes or replaces items already in the live bucket.
- Data Entries (Rows): Your first publish copies all rows you created in Test data to Live data, including user accounts. Later publishes copy only new Test data rows. Edits and deletions to existing Test data rows don’t reach Live data. Seed data that Hostinger AI Builder adds with your data structure is set up on your live website separately. On projects that existed before October 15, 2026, Test data rows created before your project was updated aren’t copied.
Push structural schema updates live via publishing
Data structures (such as a new role field or a custom table column) must be identical across both buckets. If a field exists in your test data view but is missing from your live production dashboard, your live structure needs an update.
- Open your Hostinger AI Builder editor and navigate to your project’s database table view.
- Confirm that the new structural properties (such as custom columns or fields) are correctly configured in your test data view.
- Click the Publish button in the top-right corner of the editor to republish your project. This triggers a full project republication — not just a database update — which syncs your live data structure to match your current test environment.
- Once publishing completes, your live database schema will mirror your test data structure. Existing Live data rows stay unchanged, and new Test data rows are copied to Live data after the schema update.
Structural updates require a full project republication to sync successfully, and existing Live data rows stay unchanged when you publish. If a new data column is missing on your live Hostinger AI Builder site, publishing your latest changes will bring the live schema up to date.
NOTES
- Unpublished Drafts: If you add new parameters or properties to a data table inside Hostinger AI Builder but exit without publishing, the live site’s database structure will lag behind, resulting in missing fields on the live application.
- Hostinger AI Builder Product Isolation: Hostinger AI Builder operates on an entirely automated, non-file-based architecture. Standard hosting dashboard tools in Hostinger dashboard (like File Manager backups or manual database migration wizards) do not apply to Hostinger AI Builder data tables.
- Legacy Projects: This synchronization behavior applies to the integrated backend only. If your project was built on the older Supabase backend instead, see troubleshooting Supabase configuration issues.