Qlik Cloud Reload

Qlik Cloud Reload

Certified

Trigger a Qlik Cloud app reload

Starts a reload of a Qlik Cloud app through the Reloads REST API and, by default, waits for it to reach a final status, streaming the reload log to internal storage. On success it emits a Custom asset (io.kestra.plugin.qlikcloud.assets.App) so downstream tools can track the app's freshness; asset emission is a no-op on Kestra OSS. It also requires assets.enableAuto: true on this task (a Kestra core setting, defaulting to false) — without it, the asset is silently dropped even though emitAssets defaults to true.

yaml
type: io.kestra.plugin.qlikcloud.apps.Reload

Reload a Qlik Cloud app by id

yaml
id: qlik_reload_by_id
namespace: company.team

tasks:
  - id: reload
    type: io.kestra.plugin.qlikcloud.apps.Reload
    tenantUrl: https://mytenant.eu.qlikcloud.com
    apiKey: "{{ secret('QLIK_API_KEY') }}"
    appId: 60f2e3b1a1b2c3d4e5f6a7b8
    assets:
      enableAuto: true

Reload a Qlik Cloud app by space and app name

yaml
id: qlik_reload_by_name
namespace: company.team

tasks:
  - id: reload
    type: io.kestra.plugin.qlikcloud.apps.Reload
    tenantUrl: https://mytenant.eu.qlikcloud.com
    apiKey: "{{ secret('QLIK_API_KEY') }}"
    spaceName: Sales Analytics
    appName: Sales Dashboard
    assets:
      enableAuto: true

Partial reload with reload variables

yaml
id: qlik_partial_reload
namespace: company.team

tasks:
  - id: reload
    type: io.kestra.plugin.qlikcloud.apps.Reload
    tenantUrl: https://mytenant.eu.qlikcloud.com
    apiKey: "{{ secret('QLIK_API_KEY') }}"
    appId: 60f2e3b1a1b2c3d4e5f6a7b8
    partial: true
    variables:
      START_DATE: "2024-01-01"
      END_DATE: "2024-01-31"
    assets:
      enableAuto: true

Fire-and-forget reload, without waiting for completion

yaml
id: qlik_reload_fire_and_forget
namespace: company.team

tasks:
  - id: reload
    type: io.kestra.plugin.qlikcloud.apps.Reload
    tenantUrl: https://mytenant.eu.qlikcloud.com
    apiKey: "{{ secret('QLIK_API_KEY') }}"
    appId: 60f2e3b1a1b2c3d4e5f6a7b8
    wait: false
Properties

API key

A Qlik Cloud API key, or a pre-obtained OAuth 2.0 access token: both are sent as-is in the Authorization: Bearer header. Generate an API key from the tenant's Management Console (Identity & access > API keys).

Qlik Cloud tenant URL

The tenant root URL, e.g. https://mytenant.eu.qlikcloud.com. Do not append /api/v1.

App ID

Qlik Cloud app identifier. Mutually exclusive with spaceName + appName.

App name

App name, resolved together with spaceName. Mutually exclusive with appId.

Defaulttrue

Emit an app asset

If true (default), emits a Custom asset for the app after a successful reload; set to false to opt this task out even when asset emission is otherwise enabled. This is a per-task opt-out on top of Kestra's own assets.enableAuto gate (default false): both must be true for the asset to actually be recorded — emitAssets: true alone does nothing without assets: { enableAuto: true } on this task. No-op on Kestra OSS regardless.

DefaultPT4H

Max wait duration

Ceiling for waiting on completion. Default PT4H (Qlik Cloud reloads are capped at about 3h). On timeout the task fails with the last known status; the remote run is NOT canceled.

Defaultfalse

Partial reload

If true, performs a partial reload instead of a full one. Default false.

DefaultPT10S

Poll frequency

Interval between status checks when waiting. Default PT10S; cannot usefully go below 1s (Qlik Cloud rate limits).

Defaulttrue

Reattach to an in-flight or already-finished run

If true (default), the task remembers the run it triggered (keyed by this taskrun id) and, on a worker restart or a manual Restart, adopts it instead of triggering a duplicate: a still-running run resumes polling, an already-finished run is adopted as-is. A stored id no longer found on Qlik Cloud (404) logs a warning and triggers a fresh run. The trigger call itself is never blindly retried on an ambiguous failure (e.g. a timeout), since that could create a duplicate run; the failure surfaces so a flow-level retry or a manual restart can safely re-attach or re-trigger.

A manual Restart of an execution on the same flow revision keeps the original taskrun ids, so this remembered run is still found afterward. In particular, after a maxDuration timeout or a wait: false return, the remembered entry is deliberately kept (the remote run may still be in progress): a later Restart of that taskrun then reattaches to it instead of triggering a fresh one. To force a brand-new run on the next attempt regardless of what is remembered — for example after fixing the app or automation itself — set reattach: false for that attempt, or clear it by giving the task a different id (a flow update that changes the taskrun id).

Space name

Name of the Qlik Cloud space containing the target resource, used together with its name property. Ignored when the id is set.

Reload variables

Variables passed to the app's load script. Qlik Cloud accepts at most 20 entries, each key and value up to 256 characters.

Defaulttrue

Wait for completion

If true (default), polls Qlik Cloud until the run reaches a final status.

Reload queue weight

Queue priority for the reload, from 1 (lowest) to 10 (highest). Left unset, Qlik Cloud applies its own default.

App ID

Resolved app identifier — useful when the app was targeted by name.

App name

Formatduration

Duration

Only set when wait is true and the reload reached a final status.

Formatdate-time

End time

Only set when wait is true and the reload reached a final status.

Formatdate-time

Last reload time

Freshness timestamp reported by the app after a successful reload.

Formaturi

Log URI

Internal storage URI of the full reload log, when it could be fetched.

Reload ID

Qlik Cloud identifier of the triggered reload.

Space ID

Id of the Qlik Cloud space containing the app.

Formatdate-time

Start time

Reload status

One of QUEUED, RELOADING, CANCELING, SUCCEEDED, FAILED, CANCELED, EXCEEDED_LIMIT.