Offline Mode

Offline Mode lets end-users work seamlessly with Skuid pages even when they do not have an internet connection. Changes to models and records are cached while the user is offline; when internet access is restored, these changes are sent to the appropriate data source.

Admins can activate or deactivate Offline Mode as a global setting for a site or org. Offline Mode works with all data source types, and with most components. The following components, however, will not work with Offline Mode (meaning that these components may not load into the page, or behave as expected, while the user is offline):

  • Chatter
  • Search
  • File Upload
  • Geocharts


Offline Mode is a runtime experience only. It is not possible to build Skuid pages while offline, though pages in Preview can be updated and cached while offline.

Activating Offline Mode

Offline Mode is deactivated by default. To activate it:

In Skuid Platform [[]]

  1. Navigate to Configure > Site > Offline.
  2. Check Active.

In Skuid on Salesforce [[]]

  1. Navigate to Configure > Org Preferences > Offline Mode.
  2. Check Activate Offline Mode.
  3. Create the initial manifest by clicking Create/Update Application Manifest.

Using Offline Mode

Offline Mode is available for Skuid Platform and Skuid on Salesforce (Classic and Lightning Experience). While there are some minor variations in the runtime experience based on the platform used (see below), all users will enjoy the following features:

  • Offline notification: Skuid displays a notification at the top of the page indicating that the user is “Currently Offline.”

  • Syncing: When again connected and logged into the Skuid site, Skuid displays a notification at the bottom of the page that it is syncing (to the appropriate data source) any changes made while offline. If no changes were made while offline, this notification will not show.

    • Reload any page to start syncing changes on all pages.

    • Multiple changes will take longer to sync than a few changes.


      Changes to the data are saved in the cache, but syncing those changes to the data source does not automatically occur when the user goes back online. The user must also be logged into the Skuid site to trigger data syncing.

  • Conflict resolution: If one user makes changes to the page while online, and a different user makes changes to the page while offline, Skuid will notify the offline user—once they are back online—that there are conflicts. Skuid will ask if they want to …

    • Send the changes, which will overwrite those made by the online user.

    • Cancel the changes.


      If this option is chosen, any and all changes made while offline will be canceled, not just the changes that had conflicts.

Offline Mode’s cache requirement

For a page to be available offline, the user has to have visited the page while online at some point, so the page is included in the cache. If the page is not included the cache, the user cannot save offline changes to it.


“Incognito” and other private browsing modes do not store a cache, so users working within these modes will not able able to use Offline Mode.


  • If you clear the cache, pages will not be available until you visit them again while online.
  • If you clear all temporary internet files, the Skuid cache will be deleted as well, meaning any unsynced data updates will be deleted.
  • The cache—i.e. any unsynced data—will be held for one week (7 days) only.

Performance Differences with Skuid Platform

Refreshing [[]]

After making changes made to a page while in Offline Mode, those changes can be displayed by refreshing the page.

Caching [[]]

When Offline Mode is set, Skuid prioritizes caching pages. So, if a user is online and visits a new Skuid site domain, Skuid will cache the Javascript files needed to run Skuid for that entire domain. Since Skuid runs multiple files, this process could take up to 20 seconds (depending on the speed of the network connection). The process is performed in the background and will not affect page load times.


This process only happens when an update is needed or a user visits the domain for the first time in that browser.


If you clear the cache, pages will not be available until you visit them again while online.

Performance Differences with Skuid on Salesforce

Lightning Experience [[]]

In Offline Mode, users can make changes to previously-visited pages and save those changes, but they cannot display those changes by refreshing the page. Refreshing will produce a Salesforce “offline error.” However, the saved changes will display once the user is back online.

Salesforce1 [[]]

Unlike with Salesforce Lightning, Salesforce1 users can make and save changes to Skuid pages in their Salesforce1 app, then refresh the page to see those changes displayed. Users will also be able to visit pages they have already visited while offline.

Salesforce Classic / Visualforce [[]]

In Offline Mode, users can make changes to previously-visited pages and save those changes, but if they refresh the page while offline, the refreshed page will not display. The data is still cached, but the user cannot see it.

However, utilizing the skuid:page Visualforce deployment method while setting the manifest attribute will enable users to refresh the page while offline.

If you are already using the skuid:page Visualforce component for your Visualforce overrides, you’ll just need to add manifest="{!$Resource.AppManifest}" to your markup.

For example:

    <skuid:page page="MyOfflinePage" />

If you are not already using skuid:page Visualforce overrides or would like more examples:

  1. Complete the prerequisite steps listed in the skuid:page Visualforce component topic if you have not already done so.
  2. Use the Visualforce markup form and enable Allow data refresh in Offline Mode? to generate proper Visualforce markup for your overrides.


If the page properties Show Salesforce Header and Show Salesforce Sidebar options are true, the page will not function in Offline Mode. Ensure that these properties are false for any page that you wish to be available offline.

Caveat: XML caching [[]]

Similarly, page XML is aggressively cached; however, there is no “client side” setting for pages. If you make changes to a page that is offline enabled, you need to:

  1. Navigate to Configure > Org Preferences > Offline Mode.
  2. Check Create/Update Application Manifest.

This refreshes that page’s XML instead of using a cached response, so that users will get the most recent updates to that page the next time they visit it.


This must be done every time a page is updated and those changes are deployed, or users will not see administrator updates to the page.

Because of this, Skuid recommends that you do not set a page to Offline Mode until you have completed making page changes.