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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
_AnonymousUser
Specialist III
Specialist III

[resolved] OnSubjobOk is not working as expected

Hi All,
I have multiple subjobs with the components tFixedFlowInput, tFlowtoIterate & tRunJob.
When I use OnSubJobOk on tFixedFlowInput to another tFixedFlowInput of another subjob, it is not working as expected. The other jobs are running fine though the subjob is throwing an error.
FYI, I have selected "Die on child error" option in tRunJobOk component.

Thanks,
Siva
Labels (2)
15 Replies
Anonymous
Not applicable

Hi Shong,
Thanks for your time.
I'm using the v5.3.1.
Is there any way to work it in the above mentioned version. It would be really helpful to me if you provide the way to work it in the v5.3.1.

Regards,
Siva
Anonymous
Not applicable

Hi Siva
I have tested this problem in the v5.3.1 and I got the same problem, it was a bug which only occurs when 'Enable parallel execution' box is checked on iterate link, it works normal if this box is not checked. So, you can resolve this issue with one of the following ways:
- Disable parallel execution on the iterate link.
- Upgrade to the new release if you are using community version, or open a ticket in our support portal to request a patch if you are using Talend enterprise product.
Shong
Anonymous
Not applicable

Hi Shong,
Thanks for your response.
I can't disable the parallel execution on the iterate link as it is one of the most important part in my business process.
I have tried few things to get the same behavior of OnSubjobOk. But those are working in some scenarios & failed in some other scenarios.
Is there any possibility to have a Skype Call/ Web Call with you ? It would be really helpful to me.

Thanks
Siva
Anonymous
Not applicable

Hi Siva
If you don't plan to upgrade your studio to a new release, you have to redesign the job to avoid this issue, the workaround can be:
- Define a flag in the child job to indicate the job runs fine or failure.
- Read this flag in the main job, and use runIf connector instead of onsubjobok, to fire other processing based on the condition.
Refer to this KB article:
Can I define a variable that is accessible from multiple Jobs?
Shong
Anonymous
Not applicable

Hi Shong,
Thanks for your response.
I already implemented the same flag kind of idea by creating one global variable. It's working fine.

Regards,
Siva
Anonymous
Not applicable

Hi Shong,
Thanks for your response.
I already implemented the same flag kind of idea by creating one global variable. It's working fine.
Regards,
Siva

Great! Thanks for your feedback, this topic can be marked as resolved now.
Shong