I use my app_config to control the number of (to-be-crunched) WUs of all types: CPU-WUs and GPU-WUs. Anyway, I recall that if there is no config reference to a WU in an app_config, that WU passes through as if there was no app_config -- although here, controlling the crunch-scheduling would not be possible. I'll reserve that control come the availability of production-WUs and I would then need the code to avail of that control.
;
; andzgridPost#826
;

@ andzgrid, I was thinking the same too because non of my GPU crunchers received any (they are all using app_config).

Your case may be just a matter of beta-WU unavailability (where app_config has no bearing) as far as reception of those WUs go for machines that are enrolled in the beta testing. As far as the matter of having a received WU be crunched, there is where an app_config (or its absence) figures in. I'm pondering about these matters as I type...
;
; andzgridPost#827
;

Picked up 6 wu. 5 completed and are pending validation. One is still running and should finish in about 3 hrs.

I have just received 8 WU's, 7 currently running high priority but I have noticed that all 7 have run up to about 4% and are now cycling up to about 4.3% and then dropping back to 3.0/3.5% and climbing back to about 4 - 4.5% before starting the 'staircase cycle' again - been doing this for 12 minutes so far....it doesn't look like normal behaviour to me.....