---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Configure offline cache to devices

# Configure offline cache downloads to user devices {#ariaid-title1}

* Release version: Australia
* 
* Updated June 1, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Control when and how the offline cache is refreshed on user devices to maintain relevance, performance, and bandwidth efficiency.
ServiceNow mobile supports four refresh options, which can be used individually or in combination. Combine incremental updates, scheduled refreshed, triggered downloads, and manual on-demand update refreshes, for a balance of data
relevance and preservation of battery life.

Scheduled offline caching
:
    * Downloads data automatically at defined intervals, such as once a day at midnight.
    * Verify devices have current data without requiring user action.

    {#offline-cache__ul_nbj_4k2_njc}This method provides a predictable, admin-controlled refresh cycle. For more information, see [Scheduled offline caching](https://servicenow-prod.fluidtopics.net/zH6_eBpRIs~gkrgMI6Lxhg "Schedule automatic cache downloads at defined intervals, to keep offline data current and consistent. This approach prepares users for working offline at specific times without requiring them to manually download the cache.").

Incremental automatic download
:
    * Automatically downloads only the changes since the last sync, rather than the full dataset. Changes include the addition, deletion, or updates of records.
    * Runs in the background more frequently without heavy data loads.

    {#offline-cache__ul_vq3_sk2_njc}This method keeps data current with minimal bandwidth and faster syncs. For more information, see [Incremental offline caching](https://servicenow-prod.fluidtopics.net/Bc4Q_i1BTqJZiq~smGRcCg "Incremental offline synchronization downloads only the changes to records, rather than the full dataset. This approach keeps offline data current while reducing network and battery usage.").

Button-triggered download
:
    * Buttons can be configured to initiate a cache refresh after it is tapped. The flow is when the user taps the button, the action completes, and the app automatically updates the offline data cache.
    * Useful in offline-first environments where stale cached data could lead to invalid operations, helping keep the offline cache current and reliable.

    {#offline-cache__ul_hv5_vk2_njc}This method reduces the risk of errors such as referencing outdated records by ensuring the cache is updated before the transition to offline mode. For more information, see [Cache updates triggered by user actions](https://servicenow-prod.fluidtopics.net/3ZYe1ed10fqK6Gg_ai_gmQ "Use action-triggered cache updates to define specific user actions that automatically refresh the offline cache in the background. This process reduces reliance on manual cache updates and helps to verify that users have current data when its needed.").

On-demand manual download
:
    * The user manually triggers a cache download or refresh as needed.
    * Useful when users need control over when data is updated, for example before entering an area without connectivity.

    {#offline-cache__ul_n34_gk2_njc}This method saves bandwidth by updating data only when the user chooses. For more information, see [Manual offline caching](https://servicenow-prod.fluidtopics.net/_8jNQQw0kUlbU0iVTKCKzQ "Users can manually download or refresh the offline cache at any time. This option gives users control over when their device data is updated, before working without connectivity.").
* **[General guidelines for handling cache downloads](https://servicenow-prod.fluidtopics.net/lpmr_5v9W60Feuoi98t4jg)**   
  When working with cache downloads keep these general guidelines in mind for usability and a good user experience.
* **[Scheduled offline caching](https://servicenow-prod.fluidtopics.net/zH6_eBpRIs~gkrgMI6Lxhg)**   
  Schedule automatic cache downloads at defined intervals, to keep offline data current and consistent. This approach prepares users for working offline at specific times without requiring them to manually download the cache.
* **[Incremental offline caching](https://servicenow-prod.fluidtopics.net/Bc4Q_i1BTqJZiq~smGRcCg)**   
  Incremental offline synchronization downloads only the changes to records, rather than the full dataset. This approach keeps offline data current while reducing network and battery usage.
* **[Cache updates triggered by user actions](https://servicenow-prod.fluidtopics.net/3ZYe1ed10fqK6Gg_ai_gmQ)**   
  Use action-triggered cache updates to define specific user actions that automatically refresh the offline cache in the background. This process reduces reliance on manual cache updates and helps to verify that users have current data when its needed.
* **[Manual offline caching](https://servicenow-prod.fluidtopics.net/_8jNQQw0kUlbU0iVTKCKzQ)**   
  Users can manually download or refresh the offline cache at any time. This option gives users control over when their device data is updated, before working without connectivity.