Hi KarenTH
Jobs in job queue have new property called Inactivity Timeout. When job detects there's nothing to process in 2 subsequent runs it gets set to On hold due to Inactivity state in order to avoid them from running constantly and not processing anything.
By setting Inacitvity timeout, you set the period after which job will be "woken up" automatically from On hold due to inactivity state. If Inactivity state is set to 0 job will stay in On hold due to inactivity state until user starts them. The process is as follow:
1. Job gets executed
2. Job has nothing to process
3. Job gets executed again
4. Job has nothing to process
5. Job gets to On hold due to inactivity state until Inactivity timeout expires
6. Job gets executed when inactivity timeout expires.