09-07-2015 12:06 PM - edited 03-01-2019 09:16 AM
Hi Experts,
I would like to know the solution for the below Scenario :
I am trying to set the Tidal job rerun the same occurrence multiple Times. I would need my Job A under the Parent group which is running from 7AM to 7PM rerun on a hourly basis.
I am setting the rerun same occurrences in a hourly basis. Job B is dependent on Job A's Completion (Either normally/Abnormally) and a File dependency.
During the 1st run Job A and Job B are completing successfully but on 2nd Run ; When job A is stuck up on Waiting on dependencies which is making the Job B also to be stuck up on Waiting on Dependencies.
I could see the Job A getting started Hourly but it is still Waiting on Sependencies even though i could see the File is being moved to Job B's input Successfully.
Please help. Thanks in Advance !!
Solved! Go to Solution.
09-10-2015 08:43 AM
Hi Ram,
I believe the result would be the same, because Job B has a variable dependency AND job dependency on A. While the variable dependency may be met, but Job A almost immediately switches from Completed Normally to Waiting on Dependencies -- it may not be enough time for Job B to detect that normal completion state.
How about dropping the job dependency on A, and just use the variable dependency?
When Boolean is set to true, then job B runs.
BR,
Derrick Au
09-08-2015 06:54 AM
What dependency is it waiting on?
Can you set thing such that job B is called by an action triggered by the successful completion of job A?
09-09-2015 10:50 AM
Job A functionality which is a FTF is running Every hour as expected when i set the rerun same occurrence with 60 Min time gap to Job A but the status remains in 'Waiting on Dependencies' even if the files are picked up and moved. Hence Job B which is waiting for Job A's completion is not triggered.
When i am checking the Job A's dependencies tab ->It shows the Job A is waiting on dependencies for the Time schedule . Since the job group is configured as 7AM -7PM.
09-09-2015 11:49 AM
Hi Ram,
So there are a couple of ways to do this, one was already mentioned earlier by Joe Fletcher. When Job A completes normally then have a job action to launch Job B into the schedule. But doing so, will increase your job instances by +12 on the job activity view (since these are jobs that run every hour from 7AM to 7PM).
Another way is to create a Boolean variable and initialize it to FALSE. When Job A completes normally then have a variable action to set Boolean variable to TRUE and then status will go back to waiting on dependencies. Add variable dependency, variable action on Job B, when it sees the variable equals to TRUE, then run -- when job completes normally then have a variable action to reset the Boolean variable to FALSE.
BR,
Derrick Au
09-10-2015 08:23 AM
Thanks a lot for the reply. this does helps me.
Is it possible to change the Boolean variable value when te job is waiting on dependencies.
My job A is not getting completed normally and as soon as it is getting launched, it moves to waiting in dependencies . if I can trigger job B if job a waiting in dependencies, I can complete my development.
09-10-2015 08:43 AM
Hi Ram,
I believe the result would be the same, because Job B has a variable dependency AND job dependency on A. While the variable dependency may be met, but Job A almost immediately switches from Completed Normally to Waiting on Dependencies -- it may not be enough time for Job B to detect that normal completion state.
How about dropping the job dependency on A, and just use the variable dependency?
When Boolean is set to true, then job B runs.
BR,
Derrick Au
09-09-2015 06:32 AM
Hi Ram,
If you want Job B to run when Job A completes normally or abnormally AND file dependency is met, then in your job definitions -> Dependencies -> Select: ALL MUST BE MET
else if you want Job B to run when either Job A completes normally or abnormally OR file dependency is met, then in your job definitions -> Dependencies -> Select: AT LEAST ONE MUST BE MET
BR,
Derrick Au
09-09-2015 12:23 PM
I would create a group job for jobs A and B, them rerun the group every hour 7 am - 7 PM
09-10-2015 08:27 AM
The job A is moving to waiting in dependencies as soon as it is getting launched. Even though the functionality at the backend to move the file is working . the job is not changing the status to completed normally / abnormally.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide