LLMs.txt directory

Browser caching for faster Liveboard loads

Learn how browser caching makes Liveboards load more quickly, and how to select which Liveboards use it.

Browser caching for Liveboards reduces load times on repeat visits by storing a snapshot of Liveboard data in the user’s browser. When a user revisits a Liveboard, ThoughtSpot serves chart data from that cache instead of re-querying the data warehouse, eliminating the longest part of the wait.

Users can still manually refresh a Liveboard at any time to fetch the latest data. An indicator shows users when their data was last cached, so they always have visibility into the age of the data.

In the background, ThoughtSpot continues to fetch fresh data from the cloud data warehouse (CDW) on every load to update the cache for the next session. This means the cache is always one session behind.

Cache updates happen in the background and do not affect the current session.

Once caching is active for a Liveboard, users will notice the following changes:

  • Faster chart rendering on return visits. The data warehouse query is skipped. Charts still take a brief moment to render, but the overall wait is significantly reduced.

  • An indicator showing the timestamp of when the data was last cached. Cached data is at most 24 hours old.

  • A Refresh button that users can click to fetch the latest data from the data warehouse on demand. All existing Liveboard interactions continue to work exactly as before.

Scheduled Liveboards and downloaded Liveboards always show live data and are never cached.
Will enabling caching change how much I’m billed? No. ThoughtSpot still queries the data warehouse in the background on every Liveboard load to refresh the cache for the next visit. Caching improves the user experience without reducing underlying query volume.

Browser caching feature availability and configuration

Browser caching is enabled by default in ThoughtSpot Cloud release 26.9 and above. You do not need to contact support or take extra steps to make the feature visible in the Admin Portal. Org administrators will see the caching configuration toggle in the All Orgs section automatically. By default, no Liveboards are cached. Org administrators must opt-in by selecting which Liveboards to cache using Admin Settings. For details, see Configure which Liveboards to cache.

When caching is enabled for a Liveboard, ThoughtSpot is authorized to extract data from the CDW and store it in the user’s browser cache on their machine. This is only accessible to the user opening the Liveboard in their browser.

Configure which Liveboards to cache

  1. Sign in to ThoughtSpot as an Org administrator.

  2. Go to the Admin Settings tab.

  3. Under Application Settings select Homepage & App Experiences.

  4. Select the toggle to Enable Cache Liveboards for faster loads.

  5. Choose one of the following options:

    • Enable for all Liveboards

      Caching is applied across every Liveboard in the Org.

    • Enable for specific Liveboards

      Select individual Liveboards to cache. Other Liveboards load normally.

browser cache1
Administrators can change or disable this configuration at any time.

Important considerations

Data freshness:

  • Cached data is valid for up to 24 hours (the time-to-live, or TTL). This value is fixed and cannot be configured in the current release.

  • The cache is always one session behind. Every time a user opens a Liveboard, ThoughtSpot fetches fresh data in the background and stores it as the cache for the next visit. The data shown in the current session reflects what was fetched during the previous session.

User-specific cache:

  • The cache is private to each user and stored in their browser only. One user’s cache is not shared with or visible to other users.

Permissions are always enforced:

  • Browser caching never bypasses security rules. All row-level security, column-level security, and access controls are always respected. If a user’s permissions change, the Liveboard reflects those changes on the next load.

Automatic cache invalidation:

  • ThoughtSpot automatically invalidates the cache when any of the following occur:

    • A chart or visualization in the Liveboard is edited.

    • A Liveboard update is saved.

    • Any filter or parameter value changes in the Liveboard.

      After invalidation, the next Liveboard load fetches fresh data from the data warehouse and rebuilds the cache.

Limitations

  • The cache TTL of 24 hours is not configurable in this release.

Frequently asked questions

What happens if a user’s browser storage is full?

ThoughtSpot handles this automatically. If browser storage is low, expired cache entries are cleaned up first. If caching still cannot complete, the Liveboard loads normally from the data warehouse. The user simply does not get the speed benefit for that session.

Can I disable caching for a specific Liveboard?

Yes. Org administrators can exclude individual Liveboards from caching, or disable the feature entirely for their Org at any time in Admin Settings.

Can I disable caching for an instance?

Yes. Instance administrators can disable caching for an instance at any time in Admin Settings.

Does caching affect scheduled Liveboards or PDF downloads?

No. Scheduled Liveboards and downloaded Liveboards always show the latest data fetched directly from the data warehouse.

What happens if I change a filter or parameter in a Liveboard?

When you change a filter or parameter, ThoughtSpot immediately invalidates the cache for that Liveboard. The next time you load the Liveboard, fresh data is fetched from the data warehouse.