after them will produce unpredictable and unreliable results.

2. Don't set jobs to repeat faster than it takes your jobs stream to run. For example, if your job(s) take about 2 hours to run, do not set your job(s) to repeat every 1 hour when using job dependencies.

3. When using batch dependencies, if you save a job or a batch where all requirements are met, that depends on a batch that does not exists or has not been scheduled or is scheduled in the future, the job or batch will run immediately.

4. Jobs can depend on jobs that repeat at the same frequency (e.g. they are all daily jobs), or starting with version 3.50, jobs in a dependency chain can have different repeat frequencies.

5. When deciding whether a job can run, GECS determines:
         a. whether the jobs that this job depends on have run at least once
         b. that the most recent instance of the jobs this job depends on, scheduled              since the last time this job ran and before 'now' have run successfully based              on the predecessor job parameters entered for the job dependency.

If you indicate that job 2 depends on job 1 and you never create job 1, job 2 will not run, since 'the job this job depends on has never run.'

Example 1
If job 2 depends on job 1 and job1 is sceduled every day at 7:00 AM and job 2 is scheduled every day at 7:00 AM, job 2 will run each day as soon as job1 is successfully complete.

Example 2
If Job 2 depends on job 1 and job 1 is scheduled every Friday at 7:00 AM and job 2 is scheduled every day at 7:00 AM, after they've each run once, job 2 will run every day, except Friday, at 7:00 AM without waiting for any dependent job. On Friday it will run after job 1 is successfully complete.

Example 3
If job 2 depends on Job 1 and job 1 is scheduled every day at 7:00 AM and job 2 is scheduled every Monday at 7:00 AM, once each job has run once, job 2 will run every Monday after the Monday instance of job 1 is successfully complete.