Run Tasks

Last updated: 10/30/2026

The Run Tasks step starts the migrated reload tasks and task chains in Qlik Cloud and reports the result of each task.

Prerequisite steps

• Migrate Tasks

Step details

• Retrieval method:
  Tasks are identified using the description tag written during the Migrate Tasks step.
• Execution:
  • Chains are started at their entry points only. Downstream tasks follow through their triggers.
  • Disabled Qlik Cloud tasks are skipped.
• Step settings:
  • Which rows to run
  • Whether to wait for completion
  • The timeout
  • The concurrency cap
• Confirmation:
  Before a job that contains this step starts, a confirmation dialog states that reloads are real, that they consume tenant capacity, and that Qlik Cloud caps concurrent reloads at 30.
• Progress monitoring:
  While the step waits for completion, the job log reports progress once a minute: how many tasks have finished, are running, or have not started.
• Row results:
  Each task row has one of the following results:
  • Succeeded
  • Started
  • Unverified
  • Skipped
  • Failed
• Result artifacts:
  A report is generated in two formats:
  • RunTasks_{timestamp}.xlsx
  • RunTasks_{timestamp}.json
    These files are saved in the Reloads folder inside the job directory and can be downloaded from the job page. For details, see Job reports.

Notes

• The row results describe individual tasks. They are not job statuses.
• Anything over the Qlik Cloud concurrency cap of 30 reloads queues.

Related steps

• Migrate Tasks
• Validate Tasks
• Delete Tasks