Why does my data look different in the editor and on my live site?
In TeleportHQ, the editor canvas and your published site load data separately, so they can briefly disagree. The most common reasons: design or filter changes haven't been published yet, the live list or the REST API answer is cached, CMS pages refresh on their own schedule, or data you changed outside TeleportHQ hasn't been refreshed in the editor. Find your symptom below.
When TeleportHQ data changes show up
| What changed | In the editor | On the live site |
|---|---|---|
| Records edited in TeleportHQ's table editor or by the AI Assistant | Right away, on its own | On the next page load (sometimes the one after) |
| Records changed outside the editor: in your own database, sheet or API, from your live site or by a workflow | After you click Refresh on the list | On the next page load, unless the list or the API answer is cached |
| Entries in a headless CMS | After you reload the editor | Within about a minute of a visit, or when the CMS webhook is called |
| Design, bindings, filters, sorting, search and pagination settings | Right away | Only after you publish |
The live site shows old data, but the editor is up to date
The list is cached. Select the list and look under Caching in Array Mapper Settings. If Cache results is ticked, the live site serves the stored list for the time in Cache for. For the TeleportHQ database, edits clear the cache by themselves: the note reads "Cleared automatically whenever <table> changes." For other data sources, the note reads "Nothing in this project can clear this source’s cache — entries only expire after the duration above." Wait for the time to pass, or choose a shorter one and publish.
The REST API answer is cached. A REST API data source has its own Caching setting. In Data Sources, open the REST API source and look at Cache API responses. When it's on, "The published site calls this API at most once per duration and answers every request in between from the cached response. Changes made in the API show up once the duration runs out." Turn it off, or choose a shorter Cache for, then publish.
The content comes from a headless CMS. Your live CMS pages refresh their content at most about once a minute, when someone visits them. If you turned on the CMS webhook without a Cache revalidate period, they only change when your CMS calls the webhook, or when you publish. See How to update your site's content without republishing (CMS webhook).
You changed the design or a filter but didn't publish. Settings like bindings, filters and sorting reach the live site only after you publish. See Why don't my changes show on my live site?
The editor shows old data, but the live site is up to date
You changed data outside the TeleportHQ editor, for example in your Supabase dashboard or a Google Sheet, or a visitor or a workflow added it on your live site. The canvas doesn't know yet.
- Select the list (Array Mapper) or the Table.
- In the right panel, click Refresh (tooltip "Fetch fresh data from the data source"). On a list, it's at the right of the Array Mapper Settings title; on a Table, next to Refresh data.
If you added new tables or columns, also refresh the data source itself. See How to refresh, edit or remove a data source.
Search doesn't work while I edit
On the canvas, a click on a search box selects it instead of typing in it. Click Preview in the bottom toolbar and search there, or try your published site. See How to add search to a list.
The editor shows a different page of the list, or no items
- Preview Page only changes which page the canvas shows, not the live site.
- Override State in UI State may be on, showing the empty or loading design. Turn it off. See How to design loading, empty and error states.
- On a details page, the canvas shows the item picked with the item button at the top left. Pick another item to compare.
- A condition hides an element because of the value the editor uses for a state (its Internal value). Visitors start with the state's Default value. See How to show or hide elements based on a condition.
A filter works in the editor but not on the live site
The editor and the published site apply filters with separate code. First publish again, so the live site has your latest filter and TeleportHQ's latest fixes: for example, a Paginated list now keeps its filter groups and OR filters when a visitor moves to another page, from your next publish. If it still differs, see the known differences in How to filter a list. Contact support at hello@teleporthq.io with the page link if one of them affects you.
Pages that use the TeleportHQ database stopped showing data
- The database may be inactive. On a trial, or once a subscription has ended, a TeleportHQ database stays active for 7 days, then becomes inactive. Pro and Premium keep it active. See TeleportHQ database limits by plan.
- The site isn't hosted on TeleportHQ. "The TeleportHQ Database is designed to work exclusively with projects published through our platform. If you download the project code, the database connection will not work outside of TeleportHQ's hosting environment."
A Supabase table is empty on the site but has rows
Supabase Row Level Security may block reading. Add a policy that allows SELECT on that table. See How to connect Supabase.