Loop Statement in Qlik Compose, tasks take longer than expected to load data

sureshkumar — Mon, 08 Apr 2024 07:53:29 GMT

Qlik Compose logs statements such as:

2024-03-11 18:38:24.056 [engine ] [INFO ] [] PI# 36 RUN : Adding staging rows to TSTG_E2LIS_02_ITM_P

18:38:30.431 [engine ] [INFO ] [] PI# 39 RUN : Loop Back Point.
pool-2-thread-3 2024-03-11 18:38:30.431 [engine ] [INFO ] [] Loop on 35,36,37,38

Loop Statements run in an iteration manner, which can lead to performance issues and tasks taking longer to load data.

Resolution

Compose runs the process step (Adding staging rows to TSTG_E2LIS_02_ITM_P) in an iteration manner when any of the columns are not mapped. Either we have to map this column or define an expression for this column and regenerate the statements. Hence the process step will not be in the loop.

In the below example (Job E01 Initialization Map_2LIS_02_ITM) some of the columns are not mapped
In the Task Statements, we see the Loop Statements
Once the columns are mapped and the task statements regenerated, the loop statements are removed

After mapping the missed columns, the task can be able to load the data faster.

Cause

Compose runs the process step (Adding staging rows to TSTG_E2LIS_02_ITM_P) in an iteration manner when any of the columns are not mapped.

Internal Investigation ID(s)

QB-21468
QB-25783

Environment

article Loop Statement in Qlik Compose, tasks take longer than expected to load data in Official Support Articles

Loop Statement in Qlik Compose, tasks take longer than expected to load data

Resolution

Cause

Internal Investigation ID(s)