Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Join us at Qlik Connect 2026 in Orlando, April 13–15: Register Here!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Reshmaf
Contributor
Contributor
‎2025-11-20 02:15 AM

Qlik Compose task restart leads to repeated execution of completed steps

We have a workflow consisting of multiple ETL tasks. Each task processes several interrelated entities. Currently, Compose does not provide a checkpoint feature, so if a task fails, rerunning the job starts from the beginning instead of resuming from the point of failure. This leads to repeated execution of completed steps, resulting in longer runtimes and increased resource consumption. Could you suggest a solution for this? Splitting into one task per entity is not an option for us.

Labels (1)
Labels
182 Views
0 Likes
1 Reply
Nagaraju_KCS
Specialist III
Specialist III
‎2025-11-29 01:57 AM

If I had to choose just one data integration tool for a project requiring continuous data movement across both on-premises and cloud environments, I would choose Qlik Data Integration (QDI).

  • On-Premises Sources: Good support for legacy databases (like SAP, DB2 etc) and relational databases (like Oracle, SQL Server, PostgreSQL etc).
  • Cloud Targets: Natively supports and optimizes data loading into major cloud data warehouses and lakes (e.g., Snowflake, Amazon Redshift, and Azure)
142 Views