IPAM Scan job Status question

In IPAM in the scan job status in IPAM settings, the status is "queued" and never changes. Scan trigger is automated. Last discovery shows the date probably when it was first set up.

When you chose a subnet and click on the Scan feature, it doesnt scan, it appears as if it just Qued up the scan job but wont ever run. Looks like there is multiple jobs in there as well. 

Is that normal? Is that because they were queued up run automatically and never ran? How do you kick them off and/or remove them if needed?

Orion Platform 2015.1.0, SAM 6.2.0, QoE 2.0, IPAM 4.3, NPM 11.5, PM 2.0, Storage 5.1.0, IVIM 2.0.0