View and manage app reload tasks from the hub. Manually start reload tasks or create new reload tasks with scheduled triggers to execute the reload automatically. You can also edit and delete reload tasks.
App reload tasks that are created by an administrator in QMC also display in the hub. To view the reload tasks for an app in the hub, right-click the app and select Manage reload tasks.
Information note
You must have read access to HubSectionTask and either the HubAdmin role or read access to reload tasks in the hub, set in QMC, to manage app reload tasks in the hub.
Manage reload tasks displays the following information and options:
Name: Task name.
Enabled: If the reload task is enabled or disabled. Disabled tasks cannot be managed or enabled from the hub.
Status: Displays the current status of the task. You can click to view a summary of the latest task execution. You can also click Download script log to download the script log.
Last execution: Displays when the task was last executed.
Next execution: Displays when the task is next scheduled to run.
Actions: Management option for the task. You can click to start tasks or click to stop tasks. Click to edit a task or to delete a task.
Create task: Add a new app reload task and set task properties, including creating scheduled triggers.
You can click to refresh the task view.
Creating app reload tasks
Create an app reload task in the hub. When executed, the reload task fully reloads the data in an app from the source. Any old data is discarded. App reload tasks must include a scheduled trigger to execute the reload task automatically. The trigger determines the number of times the task will run (from one to infinity) and the frequency of the reload (once, daily, weekly, or monthly). For example, you can create a trigger to reload task to run 56 times, an app on a weekly basis. Create scheduled triggers for your tasks to reload app data at a specific time, date and frequency.
You must have read access to HubSectionTask and be assigned the HubAdmin role, set in QMC, to create app reload tasks in the hub.
Do the following:
In the hub, right-click the app that you want to create a reload task for, and then click Manage reload tasks.
Click Create task.
Enter a name for the task in the Name field.
Under Execution, review the default settings and edit any of the following properties:
Select or clear Enabled to enable or disable the task. The task is Enabled by default.
Task session timeout (minutes): The maximum period of time before a task is aborted if the session times out. The default setting is 1440 minutes.
Max retries: The maximum number of times the scheduler will try to rerun a failed task. The default setting is 0.
Click Create.
In the Tasks list, under Actions, click to open the task properties.
Click Create scheduled trigger and select the properties that you want to set for the trigger.
Scheduled trigger properties in the hub
Property
Description
Trigger name
Name of the trigger. Mandatory.
Enabled
Status of the trigger. When selected, the trigger is active.
Time zone
The time zone of your operating system, at the time you create the trigger. When you save a trigger, the settings are kept, and if you move to a different time zone, the original values are still displayed. If you want to change the time zone and start time of a trigger, you need to do that manually.
Information noteFor a trigger that was created before the introduction of the time zone setting, all times and dates are by default presented in Coordinated Universal Time (UTC).
Daylight saving time
Way to account for daylight saving time.
Observe daylight saving time: This option takes daylight saving time (DST) into account. If DST is in use in the selected time zone, the execution time and date are adjusted accordingly.
Permanent standard time: This option does not take DST into account. If DST is in use in the selected time zone, the execution time and date are not adjusted.
Permanent daylight saving time: This option takes DST into account. If a time zone uses DST, execution time and date are always according to DST, even during periods when DST is not in use.
Information noteFor time zones not using DST, always select Permanent standard time.
Example:
You created a trigger for an event at 10:00 AM, while you were working in Ottawa, Canada, in January. The time zone is (GMT-0500) Eastern Time (US & Canada) and DST is used between March and November.
If you select Observe daylight saving time, a trigger set to start at 10:00 will always start at 10.00.
If you select Permanent standard time, a trigger set to run at 10:00 will run at 10:00 in the winter but at 09:00 in the summer.
If you select Permanent daylight saving time, a trigger set to run at 10:00 will run at 11:00 in the winter and at 10:00 in the summer.
Start
Start time and date:
Start time: (hh:mm)
Start date: (YYYY-MM-DD)
End
End time and date:
End time: (hh:mm)
End date: (YYYY-MM-DD)
Select Infinite to create a trigger with no end date.
Schedule
Frequency of the trigger:
Once.
Hourly. Time period between executions of the trigger. Edit Repeat after each by typing the values for:
hour(s) (default is 1)
minute(s) (default is 0)
Daily. Time period between executions of the trigger. Type a value for Everyday(s) (default is 1). For example, type 2 to repeat the trigger every second day.
Weekly. Time period between executions of the trigger:
Type a value for Everyweek(s) (default is 1).
Select one or more days under On these weekdays to determine which days the trigger is repeated (on the weeks you have specified). For example, type 3 and select Mon to repeat the trigger on Mondays every third week.
Monthly. Select one or more days under On these days to define the days when the trigger is repeated every month.
Tip noteIf you have selected Monthly and want to be sure that a trigger is repeated every month, you need to select a day no later than the 28th.
Click Create, and then click Apply to add the trigger to the reload task.
Tip noteAfter adding a trigger for a reload task, click Refresh task list in the notification message or click in the task list to see the next execution time for the reload task in task list.
Editing app reload tasks
Edit app reload tasks in the hub. For example, create a new scheduled trigger, update the task name or execution details, or edit the properties of a scheduled trigger.
Information note
You must have read access to HubSectionTask and be assigned the HubAdmin role, set in QMC, to edit app reload tasks in the hub.
Do the following:
In the hub, right-click the app with the reload task that you want to edit, and then click Manage reload tasks.
In the Tasks list, under Actions, click to open the task properties.
Edit the task properties.
You can change the task name in the Name field.
You can change the Execution properties.
Select or clear Enabled to enable or disable the task. The task is Enabled by default.
Task session timeout (minutes): The maximum period of time before a task is aborted if the session times out. The default setting is 1440 minutes.
Max retries: The maximum number of times the scheduler will try to rerun a failed task. The default setting is 0.
Create a new trigger. Select Create scheduled trigger, set the properties (see descriptions below) for the new trigger, and then click Create to add the trigger to the reload task.
Edit a scheduled trigger. In the Triggers list, under Actions, click . Set the properties (see descriptions below) and click OK to save your changes.
Scheduled trigger properties in the hub
Property
Description
Trigger name
Name of the trigger. Mandatory.
Enabled
Status of the trigger. When selected, the trigger is active.
Time zone
The time zone of your operating system, at the time you create the trigger. When you save a trigger, the settings are kept, and if you move to a different time zone, the original values are still displayed. If you want to change the time zone and start time of a trigger, you need to do that manually.
Information noteFor a trigger that was created before the introduction of the time zone setting, all times and dates are by default presented in Coordinated Universal Time (UTC).
Daylight saving time
Way to account for daylight saving time.
Observe daylight saving time: This option takes daylight saving time (DST) into account. If DST is in use in the selected time zone, the execution time and date are adjusted accordingly.
Permanent standard time: This option does not take DST into account. If DST is in use in the selected time zone, the execution time and date are not adjusted.
Permanent daylight saving time: This option takes DST into account. If a time zone uses DST, execution time and date are always according to DST, even during periods when DST is not in use.
Information noteFor time zones not using DST, always select Permanent standard time.
Example:
You created a trigger for an event at 10:00 AM, while you were working in Ottawa, Canada, in January. The time zone is (GMT-0500) Eastern Time (US & Canada) and DST is used between March and November.
If you select Observe daylight saving time, a trigger set to start at 10:00 will always start at 10.00.
If you select Permanent standard time, a trigger set to run at 10:00 will run at 10:00 in the winter but at 09:00 in the summer.
If you select Permanent daylight saving time, a trigger set to run at 10:00 will run at 11:00 in the winter and at 10:00 in the summer.
Start
Start time and date:
Start time: (hh:mm)
Start date: (YYYY-MM-DD)
End
End time and date:
End time: (hh:mm)
End date: (YYYY-MM-DD)
Select Infinite to create a trigger with no end date.
Schedule
Frequency of the trigger:
Once.
Hourly. Time period between executions of the trigger. Edit Repeat after each by typing the values for:
hour(s) (default is 1)
minute(s) (default is 0)
Daily. Time period between executions of the trigger. Type a value for Everyday(s) (default is 1). For example, type 2 to repeat the trigger every second day.
Weekly. Time period between executions of the trigger:
Type a value for Everyweek(s) (default is 1).
Select one or more days under On these weekdays to determine which days the trigger is repeated (on the weeks you have specified). For example, type 3 and select Mon to repeat the trigger on Mondays every third week.
Monthly. Select one or more days under On these days to define the days when the trigger is repeated every month.
Tip noteIf you have selected Monthly and want to be sure that a trigger is repeated every month, you need to select a day no later than the 28th.
Click Apply to save your changes.
Tip noteIf you modified a task trigger, click Refresh task list in the notification message. You can also click to refresh the task list.
Deleting app reload tasks
You must have the appropriate permissions to delete app reload tasks in the hub.
Information note
By default, the HubAdmin role cannot delete app reload tasks. Administrators can modify the permissions in QMC for the HubAdmin role to allow this role to delete tasks, or set the following permissions for a user, set in QMC, to delete app reload tasks in the hub: read permission for HubSection_Task, read permission for ReloadTask_*, and delete permission for ReloadTask_*.
Do the following:
In the hub, right-click the app with the reload task that you want to delete, and then click Manage reload tasks.
In the Tasks list, under Actions, click .
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!