If you are chaining multiple tasks it could be influence the individual start times especially if the tasks don't always do the same and/or if there are not enough resources for all running processes on your machines. Another point is if you have more running tasks as distribution engines (qvb.exe) your tasks will be queued.
Thanks for your reply.
Please Find the screenshots which will help you to understand my problem better.
->You can find in the Screenshot that for the app 01 HAL Extract P6 values,it has its last execution time at 20.30 and scheduled to start at 6.30,where as we have set the start time at 5.30 everyday and the frequency is 2.30 hrs.
->If we do the calculation it takes the trigger interval even after the end time.Is this a product feature or a bug.Can't I get the same start time everyday?
->My concern is if the start time keeps on changing for everyday for each app,then there might be a situation where we will see two applications running simultaneously because of the frequency we have given, which will increase the CPU utilization(Though it doesn't have any business impact).
I wouldn't think that it is a bug - rather that it worked as designed because the execution will happens after each 2.5 hours starting at 05:30. That meant:
Because your 2.5 hours trigger didn't fit with the 24 hours logic the start-times will change on every day. Maybe it's an option for you to adjust the trigger-interval to 2 or 3 hours and you should get the same running-times for each day.