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

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Iterate order

Hi,
I use a tFlowToIterate component.
After this component I have 2 iterate flow.
A the first, I read a table
A the second, I update this same table
My question is : There is a risk of deadlock ?
Can I be sure that my access of the table is end when I update ?
thanks a lot for your reply
Laurent
Labels (2)
5 Replies
Anonymous
Not applicable
Author

Hi,
What's your job design, could you share the screenshot with us? Could you design two subjob for you requirement, one is for read table and the other for update.In addtion, there is "Muti thread execution" can be available in job setting.
Best regards
Sabrina
alevy
Specialist
Specialist

If you have two iterate connections from the same component, one will be executed after the other not in parallel.
Anonymous
Not applicable
Author

Hi,
Thanks for your reply
I'm going to try to attach an image of my job.
If it's not work it's not a problem 😉
When I run my job, I haven't problem.
But with a lot of records, i have some doubts.
Thanks for your opinion
Best regards
Laurent
0683p000009MBBw.png
alevy
Specialist
Specialist

I'm not sure why you have doubts. The iterates are run in the order they show. The easiest way to satisfy yourself is to look at the code the job generates. But you can also use OnComponentOK triggers from one step to the next instead of multiple iterates.
Anonymous
Not applicable
Author

OK, I see, thank you