Skip to main content Skip to complementary content

Reloading app data

Apps in the Qlik Cloud Analytics hub do not update automatically when their data sources are updated. Reloading an app updates it with the latest data from the app data sources. App reloads can be manual or scheduled.

Information note You cannot reload data in the hub for apps published to the hub from a Qlik Sense Enterprise on Windows deployment. Apps published from Qlik Sense Enterprise on Windows can be reloaded using the QMC in Qlik Sense Enterprise on Windows.

For information about which users can reload data, see:

You can check the reload status of an app. This can be Success, Reloading, or Failed.

  • In list view of apps in the Last modified column.
  • In the app card in tile view or grouped view.
Information noteThe maximum reload time for an app is three hours. If an app takes longer than this to reload, it will fail and you will receive a message.

Scheduling reloading app data

You can create a schedule for data reloading in your app. The schedule can be based on frequency, date, and time, or when a dataset in the app is refreshed.

Information noteCertain actions cause the ownership of the reload schedule to change. For more information, see Ownership of reload schedules.

To set a reload schedule for an app:

  1. Click More on the app and select Reload schedule.

  2. Click Add schedule.

  3. To schedule reloads when data is refreshed, select When a dataset is refreshed in Reload the app.

    To create a time-based schedule, select any of the options under Time in Reload the app.

    Information noteIf the app does not contain a dataset that is created and refreshed by Qlik Cloud Data Integration, the Time heading and the When a dataset is refreshed option are not displayed.

Time-based schedules

When you create a time-based schedule, you can choose:

  • The frequency and interval of the reload

  • The timezone and time of day

  • How long the schedule will be in effect

  • Full or Partial reload

Repeating reloads can be set at the following intervals:

  • Daily: Set the times per day, timezone, and the time of day.

  • Weekly: Set the days of the week, times per day, timezone, and time of day.

  • Monthly: Set the days of the month, times per day, timezone, and time of day.

  • Yearly: Set the months, days of the month, times per day, timezone, and time of day.

For schedules running multiple times per day at any interval, you can also define the hours of the day within which the schedule runs. Specify a specific time for the schedule to start that day.

By default, schedules will run continuously, with no end date. You can choose to set a start date, an end date, or to only run the schedule between two dates.

Event-based schedules

You can set a schedule to reload the app when a dataset in the app is refreshed. This option is only available for apps that contain a dataset that is created and refreshed by Qlik Cloud Data Integration. For more information, see Integrating data.

Managing reload schedules

You can edit scheduled reloads for all apps that you own.

To remove a scheduled reload from an app:

  1. In the hub, select More on the app, and click Reload schedule.

  2. Click Delete.

Tenant admins and analytics admins can edit and delete scheduled reload tasks from the Management Console. For more information, see Managing scheduled reloads of app data.

Limitations and considerations

  • The reload schedule is turned off if it fails to execute five times in a row. If you own the reload schedule for the app, you will receive notifications when this happens. Notification settings can be customized for a single app, all apps in a space, or all apps in a tenant. For information about the owner of a reload schedule, see Ownership of reload schedules.

  • If the owner of a reload schedule leaves or is deleted from the tenant, another user has to take ownership of the reload schedule, or delete and recreate it. Otherwise, the scheduled reloads will fail. For more information about how to change this ownership, see Ownership of reload schedules.

  • If you have a high number of queued and executing data reload processes (and additional concurrent CPU and memory intensive processes), you might notice that some reload processes execute, in some cases, noticeably after their scheduled start time.

  • Scheduled reloads are not included for the published copy of an app. Published apps must have scheduled reloads reconfigured on the app in the managed space.

  • If you move an app with a reload schedule between spaces, the reload schedule is deleted. Recreate the schedule in the new space if required.

  • If you add or remove datasets in an app with a When a dataset is refreshed schedule, you must remove the schedule and recreate it.

  • Partial reload is not supported for When a dataset is refreshed schedules.

Ownership of reload schedules

A time-based scheduled reload runs on behalf of the user who owns the reload schedule, rather than the app owner. For the reload schedule to run successfully, the reload schedule owner must still have the correct access to the app and its data sources. Certain actions result in changes to who owns the reload schedule. The reload schedule owner is determined by the following rules:

  • When you create a reload schedule for an app that did not previously have one, you become the owner of that reload schedule.

  • If another user edits or saves an existing reload schedule, ownership is transferred to them.

  • If another user modifies the app's load script by making edits in Data load editor (or by loading data in Data manager), ownership is transferred to them in most cases. However, if this user is already the most recent user to edit the load script, the ownership of the schedule will not transfer to them.

  • Creating or modifying an app's distribution list, whether by uploading a source file in the Reporting section or by manually editing the load script, edits the load script. If you do this and you are not the most recent editor of the load script, you will become the new owner of the app reload schedule, if it has one. If you are already the most recent editor of the load script, the ownership of the schedule will not transfer to you.

Information noteIt is not recommended to use Data manager for collaboratively developing the app's data model. For more information, see Collaborative development and Data manager.

For more information about co-developing app data models, see Collaboratively developing data load scripts in shared spaces.

Partial reload

Turn on Partial reload to run a pre-defined part of the load script and update the corresponding tables. A full reload always starts by deleting all tables in the existing data model, and then runs the load script. A partial reload will not do this. Instead it keeps all tables in the data model and then executes only Load and Select statements preceded by an Add, Merge, or Replace prefix.

Partial reload must first be configured in the load script in the Data load editor. For information, see Partial reload.

Manually reloading app data

You can reload an app manually, adding a reload task to the reload queue.

  • Click More on the app and select Reload now.

Viewing reload history for an app

Reload history contains the reload history for the selected app. Use it to help troubleshoot scheduled reload issues. You can view the status, start and end times, and duration of past and current reloads. You can also view and download a corresponding log file.

There are two ways to view the reload history for an app.

  • In the list view of apps, click the date in the Last modified column and select View reload history.
  • Select Details of an app, and click Reload history.

Reload history of an app

Screenshot of the Reload History menu in Qlik Cloud. The Reload History menu displays the status, start time, end time, and duration of reloads in an app. The cancel button is also shown in the screenshot.

On the Reload history page, click the View button to view the reload summary. Optionally, you can also download a detailed log file. When the limit for the number of logs stored is reached, new logs will replace the oldest logs, on a first in, first out basis.

You might want to cancel a reload of your app if the reload is taking too long or the app has been updated with new data and you want to start a new reload. To cancel a reload, go to Reload history, and click Cancel.

You can see the canceled reload in your Reload history.

Viewing and deleting reload schedules

Tenant admins and analytics admins can view and delete scheduled reload tasks from the Management Console. For more information, see Managing scheduled reloads of app data.

Understanding timestamps: Updated, Modified date, and Last reload date

The Updated timestamp is displayed towards the bottom of each app tile in the cloud hub. It can also be viewed by selecting More on the app, then selecting Details. The same timestamp is listed in Details as Modified date. The format of the date may differ; for example, if the app was recently updated, the Updated value on the app tile may appear like: Updated 15 minutes ago.

Last reload date is viewed by selecting More on the app, then selecting Details. This value is only refreshed when the app's data is reloaded. A reload also changes the Updated and Modified date timestamp.

Modified date and Last reload date fields in app Details

Details view displays Last reload datea and Modified date timestamps

The following table lists the operations that refresh Updated (same as Modified date) and Last reload date timestamps:

Operations that refresh Updated and Last reload date values
Operation Updated, Modified date Last reload date
Reload Yes Yes
Change name Yes No
Change description Yes No
Change thumbnail Yes No
Publish app Yes No
Change owner Yes No
Change script Yes No
New sheet No No
Change sheet No No

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!