the queue logic indeed has changed significantly in AO28 exactprecisions;
* previously there was a 10s “sleep” time between requests sent to criticalcss.com, this sleep time has been removed
* only 2 new jobs can be sent to criticalcss.com, the amount of requests for status pending jobs is unlimited, but would logically also be 2 max, resulting in 4 requests per queue run being executed
* as a result of the above queue runs now take just 1 or 2 seconds instead of in 30-50 seconds, which means it should _never_ be “killed” by the PHP execution time limit
* the “request limit” has indeed been removed, but you should see a “Queue processing time limit” for which you could set a lower limit (is 30s default)?
how is critical CSS stuck? did you have a stale queue.lock-file?
frank
Frank,
You reminded me about queue.lock. I removed that. It solved it last time something like this happened so I’m hoping it does again.
Might the queue.lock file have been there from before you updated to AO28?
