10-18-2013 12:54 PM - edited 03-01-2019 09:05 AM
Hi All,
I have a specific overnight scheduling scenario that I could use some help with, details for this example are below:
1) Job A runs every day, starting 10 minutes after midnight (12:10 AM)
2) Jobs B, C, and D run every Wednesday and Friday, starting at 9 PM, and run in sequence B > C > D
- Job B runs in 1 hour (9 - 10 PM), job C runs in 1 hour (10 - 11 PM), but job D runs for 3 hours (11 PM to 2 AM next day)
2) Tidal is configured to cut over to the next day's schedule at midnight, meaning on Wednesday and Friday, job D will still be running when the next day's schedule starts
3) If job B is still running from the previous day, I don't want my daily Job (Job A) to start on the next day until Job B from the previous day has finished
If I schedule job A to start every day at 2 AM to avoid this conflict, then every Monday, Tuesday, and Thursday I'm wasting 2 hours of our schedule between 12 AM and 2 AM on the days that job D doesn't run.
Is there any way to set up dependencies like this, where my current day's Job A is dependent on the previous day's Job D?
Thanks in advance for the help!
Best Regards,
Doug M.
Solved! Go to Solution.
10-18-2013 01:17 PM
From Job Dependency definition screen, edit your dependency and select Last Occurence (instead of Match occurrence) and Date Offset 1 - this will look at the previous day
10-18-2013 01:17 PM
From Job Dependency definition screen, edit your dependency and select Last Occurence (instead of Match occurrence) and Date Offset 1 - this will look at the previous day
01-10-2016 01:56 PM
Hi,
Did you ever solve your dependency loop issue as I am battling one mow. Do you have any advise on how to approach these loop issues?
Thanks
01-11-2016 06:50 AM
Hello Fred,
I did not have a loop issue, I was suggesting a way to resolve the issue Doug had at the time. Why don't you post the issue you are having? You can also post it in Yahoo Groups (Tidal).
Thanks,
Lumi
01-19-2016 10:22 AM
Hi Fred,
Unfortunately you're not able to set a job to be dependent on itself, but there may be one way you can get this scenario to work:
Try the following:
8. Create a Job Event, JOB EVENT A:
If you set the above up correctly, the schedule should progress like this:
And the cycle continues for all 6 instances.
Try it out and let me know if it works for you, hope that helps!
05-11-2014 04:12 AM
Did you ever resolve this issue.I have the same problem too. Even with the "Last occurence" and Date Offset to 1, I am getting an error message that hte dependency will result in a loop.
01-19-2016 09:05 AM
Sorry all, I don't frequent this site but i saw a lot of views on this thread just now and figured i would mark the correct answer.
Thanks a bunch Lumi!
My scenario wasn't a loop one, it was a cross-day scheduling question with several different jobs.
For Job A starting at 12:10 every day, i added the following settings which worked:
- Date Offset 1
- Ignore Dependency if job is not in schedule - Checked
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