Jobs are put in queue, but never run (4044804)

If you experience scheduled or forced jobs not running for all Agents on a core, you may be experiencing a hung Scheduler. To determine if this is your issue, please verify the following:

1. Go to Core or Protected Machine's Events tab and click Tasks drop down.
2. Select Journal.
3. Look for job history of a Protected Machine.
4. You will see the following. In this example we have highlighted transfer related jobs:
   1. Scheduled transfers are place in queue, but never run. They eventually timeout and are deactivated.
   2. If scheduled transfer has not been deactivated and another scheduled transferred is called, it is ignored because a relevant transfer is in queue.
   3. Forced transfers are ignored because a relevant transfer is in queue.
      
5. You can further verify by looking in AppRecovery logs and finding the following examples:
   1. Scheduled transfers:
      Request for a scheduled  transfer of 'incremental' of 'C:\; EFI System Partition 1 on disk 0; Recovery Partition 0 on disk 0' of 'ADS     ' has been put in queue
      
      Transfer (entry id = f0584dca-d15d-4919-aec9-a66666ef21e1) can't start because it is blocked by another job. Transfer is delayed until the completion of blocking job.Entry detail: 
   2. Forced transfers:
      The  forced transfer of 'incremental' of 'C:\; EFI System Partition 1 on disk 0; Recovery Partition 0 on disk 0' of 'ADS     ' was ignored because the relevant transfer is in queue

Solution:

1. Go to Events tab and click Suspend Scheduler.
2. In the window that opens, click Terminate Tasks.
   
3. The hung task(s) in Scheduler will now be cleared and jobs will run normally.