Cannot get new tasks.

I recently added 2 machines to Einstein. The first pulled down some tasks.. around 200 or so, a combination of CPU and GPU tasks. Then I stopped getting new tasks, so I assumed the system was at its capacity. I then added the project on a second machine and that machine pulled down 12 tasks. Since then no tasks have been downloaded.

I thought maybe it was caused by me removing the CPU tasks that the first machine downloaded as I wasn't able to prevent them when first adding the project to my BOINC client because I was unable to change settings on the Einstein page until I had at least 1 point returned for a task. So when my first GPU task finished, I stopped CPU tasks and removed the ones I had downloaded.

Here is the output... I did a bit of goolging and also searched on these forums as well for the answer and while I found ones similar, I couldn't find one without a second issue listed like lack of GPU memory, or a high DCF. Neither of which I see here. Thoughts?

2019-05-01 01:48:12.3831 [PID=29388]   Request: [USER#xxxxx] [HOST#12775713] [IP xxx.xxx.xxx.115] client 7.12.1
2019-05-01 01:48:12.4122 [PID=29388] [debug]   have_master:1 have_working: 1 have_db: 1
2019-05-01 01:48:12.4122 [PID=29388] [debug]   using working prefs
2019-05-01 01:48:12.4122 [PID=29388] [debug]   have db 1; dbmod 1536624082.000000; global mod 1536624082.000000
2019-05-01 01:48:12.4129 [PID=29388]    [handle] [HOST#12775713] [RESULT#849898146] [WU#401641190] got result (DB: server_state=4 outcome=0 client_state=0 validate_state=0 delete_state=0)
2019-05-01 01:48:12.4129 [PID=29388]    [handle] cpu time 170.649500 credit/sec 0.010827, claimed credit 1.847668
2019-05-01 01:48:12.4129 [PID=29388]    [handle] [RESULT#849898146] [WU#401641190]: setting outcome SUCCESS
2019-05-01 01:48:12.4189 [PID=29388]    [send] effective_ncpus 4 max_jobs_on_host_cpu 999999 max_jobs_on_host 999999
2019-05-01 01:48:12.4189 [PID=29388]    [send] effective_ngpus 4 max_jobs_on_host_gpu 999999
2019-05-01 01:48:12.4189 [PID=29388]    [send] Not using matchmaker scheduling; Not using EDF sim
2019-05-01 01:48:12.4189 [PID=29388]    [send] CPU: req 0.00 sec, 0.00 instances; est delay 0.00
2019-05-01 01:48:12.4189 [PID=29388]    [send] ATI: req 2419200.00 sec, 0.00 instances; est delay 0.00
2019-05-01 01:48:12.4189 [PID=29388]    [send] work_req_seconds: 0.00 secs
2019-05-01 01:48:12.4189 [PID=29388]    [send] available disk 98.83 GB, work_buf_min 864000
2019-05-01 01:48:12.4189 [PID=29388]    [send] active_frac 0.999997 on_frac 0.931419 DCF 0.401495
2019-05-01 01:48:12.4242 [PID=29388]    [mixed] sending locality work first (0.4355)
2019-05-01 01:48:12.4246 [PID=29388]    [mixed] sending non-locality work second
2019-05-01 01:48:12.4528 [PID=29388] [debug]   [HOST#12775713] MSG(high) No work sent
2019-05-01 01:48:12.4528 [PID=29388]    Sending reply to [HOST#12775713]: 0 results, delay req 60.00
2019-05-01 01:48:12.4529 [PID=29388]    Scheduler ran 0.073 seconds