As explained in the documentation [“Dependencies among Jobs”](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/creating_and_scheduling_jobs/configuring_new_jobs/dependencies_among_jobs#dependencies-among-jobs), if Job A depends on Job B, then Job A should be scheduled to be the first job to be executed ( Job A starts at time X and Job B starts at time x+1 second). Then, “A” will be in WAITING state until “B” completes its execution (note that if “B” is already being executed when “A” starts, then “A” will be in WAITING state until “B” starts a new execution and finishes it).
For most of your configured jobs, you are seeing correct behaviour and with the same logic/configuration, the other jobs should work the same way.
I would recommend you check the update you currently have and if you are using an old update, then install the latest update as it contains several bug fixes and enhancements. You can download the update from[ “Denodo Support Site”](https://support.denodo.com/) if you are a customer with a valid support account.
Apart from that, if you notice that the behaviour is different from what is expected even with the correct configuration and the latest update, then you can submit a case if you have a valid support account. The agent can look into the configuration in place in order to find the reason for this behaviour.
For more information on how to create and schedule jobs please refer to the [“Creating and Scheduling Jobs”](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/creating_and_scheduling_jobs/creating_and_scheduling_jobs#creating-and-scheduling-jobs) section of the Scheduler Administration Guide.
Hope this helps!