One Star

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
5 REPLIES
Moderator

Re: Iterate order

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
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Seven Stars

Re: Iterate order

If you have two iterate connections from the same component, one will be executed after the other not in parallel.
One Star

Re: Iterate order

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
Seven Stars

Re: Iterate order

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.
One Star

Re: Iterate order

OK, I see, thank you