---
sourceDocument: Brazil Mobile Configuration and Navigation
sourceDocumentLink: https://www.servicenow.com/docs/r/mobile

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Configure scheduled offline caching

# Configure scheduled offline caching {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Configure offline caching so your field technicians can receive scheduled updates to
their offline data cache. Scheduled downloads are based on the user's work schedule.

## Activate the Agent Schedule plugin {#scheduled-offline-caching__section_ukz_cwm_1mb}

To enable and configure scheduled offline caching, the Agent Schedule plugin
\[com.snc.agent_schedule\] must be activated. For details on plugin activation, see [Activate a plugin](https://www.servicenow.com/docs/access?context=t_ActivateAPlugin&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).

## Create work schedules for offline caching {#scheduled-offline-caching__section_zrl_qzm_1mb}

For mobile clients other than Mobile Agent, verify that an entry in offline download schedule (sys_sg_offline_download_schedule) exists for the client type, for example, Request. This entry specifies the table that has the offline
download schedules for the agents or technicians. Mobile uses the schedule from this table for scheduling offline cache generation. To populate schedules for each user, a scheduler script can be used like in Field Service
Mobile.

For the Mobile Agent app, the entry is created when the plugin is activated. After activating the plugin, you must create work schedules for the agents or technicians to enable users to automatically receive
scheduled offline caches. This can be done directly through the Agent Work Schedules \[agent_work_schedule\] table. For more information on how to create schedules through this table, see [Create a work schedule for an agent or technician](https://www.servicenow.com/docs/access?context=create-agent-work-schedule&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US).

Based on the records from the Agent Work Schedules table, your instance runs background
scheduled jobs that create schedules in the Agent Daily Schedules \[agent_daily_schedule\] table.
Within these schedules, agents will receive a silent push sometime throughout their scheduled
day.

The offline payloads that your instance generates are based on the times recorded in the Agent
Daily Schedules. These can be found in the Events \[sysevent\] table. Use the records in the Event
table to track these payloads, and info about when they are created and when they are sent to
the agents.

## Scheduled Jobs associated with offline caching {#scheduled-offline-caching__section_lmb_bfn_1mb}

These scheduled jobs are automatically scheduled for only users who enable background
downloading on their app. For information on how users can enable this feature, see [Offline mode for mobile](https://www.servicenow.com/docs/hlJzMSrLZlFJSeMcqBQYTg "Access and submit actions to records in your mobile apps, even if you don't have an internet connection.").

Populate Agents Daily Schedule Table
:   This job runs once daily for all users with background downloading set to
    true.

Scheduled Download of Offline Payload
:   This job creates an event for the first payload of the day in the
    \[mobile_offline_payload_gen_queue\] table.

## Offline scheduling system properties {#scheduled-offline-caching__section_lfk_bfn_1mb}

Use the following properties on the System Properties \[sys_properties\] table to configure scheduled offline caching.
{#scheduled-offline-caching__table_dtt_lgn_1mb__entry__2}

| Property | Description |
|-|-|
| glide.sg.offline.scheduled_download.enabled | Enables scheduled downloading for all Mobile Agent app users. |
| glide.sg.offline.scheduled_download.cachesync_offset | Defines the number of minutes before the user's scheduled time that the instance begins generating the offline payload. |
| glide.sg.offline.scheduled_download.reminder_offset | Define the number of minutes before the user's scheduled offline time that a reminder is sent to download the cache manually. |
| glide.sg.offline_payload.refresh_frequency | Define a fixed interval between the initial scheduled cache download and when the cache should be refreshed. |
| glide.sg.offline.attachment.max_total_bytes | Defines the total amount of storage the offline cache can use for attachments in bytes. |
[Table 1. Offline scheduling system properties]

{#scheduled-offline-caching__table_dtt_lgn_1mb}

For information on other related offline system properties, see [System properties in offline mode](https://www.servicenow.com/docs/JHSHNc9TH~wNlb79Uoz~4w "Use the table to view system properties related to offline mode.").
* **[General guidelines for scheduling offline caching](https://www.servicenow.com/docs/71iy1LH_sTXBSHIejx~zCw)**   
  When scheduling offline caches keep these general guidelines in mind for usability and a good user experience.