Update Queue malfunction?

[PhoenixIncarnate]

I've been attempting to update my site because previously it wasn't working correctly with Autokeen (my fault). After making my updates I've been submitting them to the Queue as directed in the help topics.

Now, I've noticed some funky things about the Queue, and at first I thought it was just me but now I'm convinced there is something wrong.

It appears to me that my updates are being constantly pushed to the back of the Queue - like I'm on hold or something. This happened just now (14:02:58 according to server time). I submitted an Index Only update 15 minutes ago - at that time, I saw 0 jobs in Queue, and when I made my submission the Queue changed to 1 waiting. At this point in time, my job is still waiting, but now there are 45 jobs ahead of me.

This same thing happened one night at the 12 AM EST job scheduling as well. I submitted just before the server's batch updates and, having not been serviced immediately, got stuck behind them all. I went from first in line to waiting behind 800-some jobs.

My understanding of a Queue is that Queues are first-in-first-out. Am I misunderstanding the display at the bottom of my screen, or am I for some reason being pushed to the back of the Queue in favor of other people's jobs?

EDIT: At the time I've finished typing this post - 14:13:46 server time - all 45 jobs ahead of me have finished. My job is still sitting in the Queue by itself, not being serviced.

[Black Sparrow]

... are you using the right sitadmin?

It sounds like you're using the old one ( http://siteadmin.comicgenesis.com:8080/ ... s/main.cgi ). I don't know if the manual updates still work on that one. Use this one.

Also, I'm sure you know not to click the update button more than once, right? Since every time you click, you do get sent to the back of the line. Otherwise, yeah, it should be first-come, first-served.

Keep in mind that updates are not immediate. They may take bit to come into full effect. Also, hard refresh the page you expect to be updated to clear out you cache.

[PhoenixIncarnate]

Hm, considering the first time I noticed it was late enough to hit the nightly batch updates, I probably did hit "refresh" without realizing it. OK, probably my own fault then. In any case everything is working now. Thanks!