Hostinger Horizons: How to troubleshoot data synchronization in Hostinger Horizons databases

When building data-driven components with Hostinger Horizons, the system separates your testing environment from your live deployment into two independent environments: test data and live data. Because these databases operate separately to protect your production environment, changes made to your data tables during drafting may not immediately sync to your live site. This guide breaks down how data environments interact in Horizons and how to synchronize them.

Understand the Two-Bucket Data Model

To correctly troubleshoot synchronization issues, it is essential to understand that Horizons isolates test schemas from live data rows to keep your live application safe:

• The Separate Bucket Concept: Think of the test and live environments as two identical iron buckets. The test bucket holds apples, while the live bucket holds bananas. Their structural shape is identical, but their contents (the actual rows of data) will always differ.
• Data Entries (Rows): Creating a mockup user or adding content rows inside your test database view is purely for preview purposes. These rows will not automatically transfer or synchronize into the public live database bucket.

Push Structural Schema Updates Live via Publishing

While content rows do not transfer between environments, 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.

1. Open your Hostinger Horizons editor and navigate to your project’s database table view.
2. Confirm that the new structural properties (such as custom columns or fields) are correctly configured in your test data view.
3. 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.
4. Once publishing completes, your live database schema will mirror your test data structure. Existing rows in each environment remain isolated and are not affected.

Data entries remain safely isolated within their respective buckets, but structural updates require a full project republication to sync successfully. If a new data column is missing on your live Horizons site, publishing your latest changes will bring the live schema up to date.