The predecessor job dependency in Denodo is configured in the Trigger section of Scheduler, which has CRON expression as a mandatory field. So I would not try to have a dependency within Denodo Scheduler but have the triggering mechanism from a different 3rd party tool. This avoids inconsistencies with the job executions.
If triggering jobs from outside is a requirement, then I would try to embed the dependencies as well in the same tool. I would also check the steps explained in [here](https://community.denodo.com/kb/en/view/document/Job%20hangs%20in%20%22WAITING%22%20state%20even%20though%20Dependency%20job%20has%20run) to see if the required dependencies and job cycles can be achieved with the Denodo scheduler itself.
Hope this helps.