---
source: https://qlik.dev/toolkits/qlik-cli/scheduling/scheduling-task-resource-reload-on-dataset-updated/
last_updated: 2026-11-16T13:31:48+01:00
---

# scheduling task resource reload on-dataset-updated

## qlik scheduling task resource reload on-dataset-updated

Create a reload task triggered by a dataset update

### Synopsis

Creates a reload task for the app that runs when a Data Integration (Qlik Talend
Cloud) pipeline finishes updating or loading a dataset (QVD or data warehouse
storage) that the app uses.
This is a convenience wrapper over `POST /scheduling/tasks`; the full task
definition is generated server-side. Use `POST /scheduling/tasks` for advanced
configurations.

Eligible datasets are resolved from the app's lineage when the task is created,
as the task owner; datasets the app starts using later are not picked up. Other
data sources, such as data files or QVDs in spaces, do not trigger the task.
An app can have only one such task, and it is shared with the app's legacy
reload-task auto-reload setting: changing that setting replaces or removes this
task's trigger. One pipeline run may start the task more than once.

Errors:

- `400` `CHO-001`: the request body or the path `id` is invalid. This includes a
  `name` or `description` over its maximum length.
- `403` `CHO-003`: the app does not exist, is not accessible, or the caller
  lacks `app:reload` on it.
- `404`: not returned for a missing app, which gets `403` as above. Kept for
  compatibility.
- `409` `CHO-031`: the app already has a dataset-update task, enabled or not. Its ID
  is returned in `value.existingTaskId`.
- `422` `CHO-030`: the app does not use any dataset produced by a Data Integration
  pipeline, or the task owner cannot see all of them.
  `CHO-014`: the app already has the maximum number of tasks.
  `CHO-018`: the caller has reached the per-user task quota, when one is configured.
- `424` `CHO-013`: the task could not be stored. Nothing is created.

```
qlik scheduling task resource reload on-dataset-updated <resourceId> [flags]
```

### Options

```
      --description string   A human-readable description of the task's purpose.
      --enabled              Whether the task is enabled. A disabled task never runs on its own. Defaults to ˋfalseˋ.
  -f, --file file            Read request body from the specified file
  -h, --help                 help for on-dataset-updated
      --interval int         Duration in seconds to wait between retries, at least 1 (default 1)
      --name string          (Required) The name that identifies the task.
      --partial              Whether the reload is partial.
  -q, --quiet                Return only IDs from the command
      --raw                  Return original response from server without any processing
      --retry int            Number of retries to do before failing, max 10
```

### Options inherited from parent commands

```
  -c, --config string            path/to/config.yml where parameters can be set instead of on the command line
      --context string           Name of the context used when connecting to Qlik Associative Engine
      --headers stringToString   HTTP headers to use when connecting to Qlik Associative Engine (default [])
      --insecure                 Allow connecting to hosts with self-signed certificates
      --json                     Returns output in JSON format, if possible. Disables verbose and traffic output
  -s, --server string            URL to Qlik Cloud or directly to a Qlik Associative Engine
      --server-type string       The type of server you are using: cloud, Windows (Enterprise on Windows) or engine
  -v, --verbose                  Log extra information
```
