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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] Resume on error

Hi,
What is the best practice to create a resume-on-error process?
For example I have this:
tFileInputDelimited --> tMap --> tMySQLOutput.
And then the primary key field is a foreign and it's parent does not exist for one of the records in the inputfile.
Above is just an example, I am NOT looking for a specific solution on the tMysqlOutput component but a more generic solution which can also be used on other components.
Thanks
Labels (2)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hi saukema
We usually finish the main processing in a child job, and use tRunJob to call the child job, uncheck the option 'die on error' on tRunJob. For example:
parent job:
tFileInputDelimited--main--tMap--main-->tFlowToIterate--iterate--tRunJobou
on tRunJob, uncheck the option 'die on error', so that the main job will continue to execute next record even though the child job has an error.
child job:
tFixedFlwInput--main--tMysqlOutput

View solution in original post

1 Reply
Anonymous
Not applicable
Author

Hi saukema
We usually finish the main processing in a child job, and use tRunJob to call the child job, uncheck the option 'die on error' on tRunJob. For example:
parent job:
tFileInputDelimited--main--tMap--main-->tFlowToIterate--iterate--tRunJobou
on tRunJob, uncheck the option 'die on error', so that the main job will continue to execute next record even though the child job has an error.
child job:
tFixedFlwInput--main--tMysqlOutput