Hi Vasudev
1. As soon as dependencies are met then job should fire off automatically. But in your case, that may not always be true. While there isn't an event to detect if a job is waiting on dependency for a specified time, you can utilize either 'Job Not Ready by Start Time' or 'Job Not Ready by End of its Time Window'
2. Which Tidal version are you using? Earlier, I had a similar issue with 6.3.4.81, where the job option to re-run whenever dependencies have been met did not work properly. The solution is to either rollback to 77 or patch to 91.
BR,
Derrick Au