Solved: Dependency task time out in QlikView - Qlik Community

Anonymous · ‎2016-07-13

Hi,

I have task1 that should trigger after 2 tasks (TaskA & TaskB) are completed (on multiple events) successfully. TaskA triggers at 12:00 am and completes around 3 am.

TaskB triggers around 5 am completes around 5:30 am. I would like to know how long the Task1 waits for its dependency task.

TaskA has another dependencies and it triggers after that so cannot change the timing of the task.

Peter_Cammaert · ‎2016-07-26

Warning: too many notes words will follow:

Concerning your first question (you changed the task identifiers from your previous post: task 1 and task 2 will now trigger task A?): imagine task A has a trigger "on multiple events complete". Each event can be a successful or failed execution. If we assume that both task 1 and task 2 have to succeed, then task A will only be triggered when both tasks complete successfully. If either one fails, task A will not be triggered. If either one takes longer to execute, then task A will only be triggered when the later task completes. There is no timeout on the Task A trigger, but there may be a timeout on task 1 or task 2 execution. Again: task A won't do anything ! It will be triggered by an external task scheduler which is called the QlikView Distribution Service. When QDS inspects tasks at hand it will check the next task to be exeuted whenever task 1 or task 2 finishes. When the last one of these two finishes, QDS considers the task A trigger conditions as fulfilled and triggers Task A. To make this happen, Task A hasn't done anything at all, it just executes.

Concerning your second question: task A will only be triggered when all 10 tasks ran to completion. If you forgot to trigger task 10, or task 10 didn't execute successfully, then you may start it by hand. When it completes, task A will still be triggered automatically because succesful exectuion of task 10 was the last missing piece to fulfil the Task A trigger conditions.

The "on multiple events completed" trigger has a parameter called "Time Constraint". It defines a window in which all dependent tasks have to complete. The default value is 6 hours. If you didn't change that value, 8 hours will be too long for Task A to be triggered automatically. See QMC Help for more details.

Hope this makes things clear.

Peter

View solution in original post

Peter_Cammaert · ‎2016-07-25

A task that triggers on multiple other tasks completing successfully is different from a task with dependencies.

As the name implies, a task that triggers on multiple events completed is triggered. It isn't waiting for anything, It is just dead all along and is kicked into action whenever the conditions for execution are fulfilled. Nevermind how long they take (assuming that you properly adjusted the timeout values for long-running jobs) Those conditions are managed by the scheduler in the QDS.

AFAIK a task with dependencies (defined in the central section of the triggers overview) will not wait at all. If one of its dependencies didn't complete successfully last time it ran, then the task with dependencies will fail.

Peter

Anonymous · ‎2016-07-25

Hi Peter,

Thank you very much for your time. My question is, If task1 is completed at 12 AM & task2 is completed at 7 AM, Does taskA will be triggered at 7 AM. What is the time that taskA looks & confirms that all its multiple tasks are completed.

Let me also put this way, I have taskA that should run after 10 tasks are completed. 9 tasks were completed successfully and 10th tasks was failed. I saw that after 8 hrs and ran the 10th task. So now, will the taskA will be triggered automatically even after 8 hrs.

Does it taskA will be triggered though its 9 tasks were completed 8 hrs back? If yes, I wanted to know this time out that how long taskA thinks that all the tasks are completed successfully.

Thanks,

Nithesh

Peter_Cammaert · ‎2016-07-26

Warning: too many notes words will follow:

Concerning your first question (you changed the task identifiers from your previous post: task 1 and task 2 will now trigger task A?): imagine task A has a trigger "on multiple events complete". Each event can be a successful or failed execution. If we assume that both task 1 and task 2 have to succeed, then task A will only be triggered when both tasks complete successfully. If either one fails, task A will not be triggered. If either one takes longer to execute, then task A will only be triggered when the later task completes. There is no timeout on the Task A trigger, but there may be a timeout on task 1 or task 2 execution. Again: task A won't do anything ! It will be triggered by an external task scheduler which is called the QlikView Distribution Service. When QDS inspects tasks at hand it will check the next task to be exeuted whenever task 1 or task 2 finishes. When the last one of these two finishes, QDS considers the task A trigger conditions as fulfilled and triggers Task A. To make this happen, Task A hasn't done anything at all, it just executes.

Concerning your second question: task A will only be triggered when all 10 tasks ran to completion. If you forgot to trigger task 10, or task 10 didn't execute successfully, then you may start it by hand. When it completes, task A will still be triggered automatically because succesful exectuion of task 10 was the last missing piece to fulfil the Task A trigger conditions.

The "on multiple events completed" trigger has a parameter called "Time Constraint". It defines a window in which all dependent tasks have to complete. The default value is 6 hours. If you didn't change that value, 8 hours will be too long for Task A to be triggered automatically. See QMC Help for more details.

Hope this makes things clear.

Peter

ashwanin · ‎2016-07-26

Hi Nithesh,

Your question : I saw that after 8 hrs and ran the 10th task. So now, will the taskA will be triggered automatically even after 8 hrs. Does it taskA will be triggered though its 9 tasks were completed 8 hrs back?

Answer is ' No'. It will not run automatically. It will run on its next scheduled time or you have to run it manually.

Anonymous · ‎2016-07-26

Thank you guys. All I wanted to know is that

"The default value is 6 hours. If you didn't change that value, 8 hours will be too long for Task A to be triggered automatically. See QMC Help for more details."

Thanks,

Nithesh