JavaScript Optimizer "queued" status

Discussion created by deleted-user-Jie3eyjOl9XM on May 21, 2014
Latest reply on May 26, 2014 by rahul_m
I've been working with the Optimizer for a couple days, and having a tough time getting everything configured the way it likes. It's a nontrivial application. At first, I just got a "queued" status. Then, for a while I was getting actual output. But, now I'm back to getting "queued". These builds remain queued for a long time, until I delete them.

I'm wondering, is there some kind of error or misconfiguration in my code that would cause the "queued" status? Or, is it really queued? Is there some kind of metering that's causing me to wait?