A waiting room that never moves is not a queue. It is a bug, or a design choice that looks like one. The queue is supposed to move people through in order. When it does not, the problem is usually in how the queue was set up, not in how many people joined it.
The number that does not move
A queue that never moves is the most frustrating experience in online commerce, because it gives you a number and then takes away the meaning of the number. You are at position 1,247. Forty minutes later you are at position 1,247. The queue is not working. It is displaying a number while nothing happens behind it.
The cause is usually a bottleneck downstream of the queue. The queue is releasing people into a checkout that cannot handle them, or into an inventory pool that is held, or at a release rate that was set too low for the demand. The queue itself is fine. The system it feeds is not, and the queue hides the failure by showing a number that never changes.
The other common cause is that the queue is not a queue at all. Some systems assign positions randomly when the sale starts, which means your position is not a place in line, it is a lottery ticket. If your number never moves, it may be because the system is not moving people in order. It is moving them in the order it chose, and your turn has not come.
Why refreshing makes it worse
The instinct when a queue is stuck is to refresh the page. That is the worst thing you can do. Refreshing usually sends you to the back of the line, or starts a new session that the system treats as a new joiner. Ticketmaster's help pages say explicitly not to refresh, and to keep the page open once you are in. The queue remembers your session. A refresh is a new session.
The same logic applies to opening the page in a second tab or a second device. The system sees two sessions from the same person and may treat one of them as a duplicate and drop it. The queue is designed for one session per person, and working around it usually costs you the place you had.
The right move is to leave the page open and wait, and to check the event's status page or social media for a notice. If the queue is genuinely stuck, the operator will usually post about it, because a stuck queue is a visible failure and the operator knows it. If there is no notice and the number still does not move after 20 minutes, the queue is broken and waiting will not fix it.
The design choices that create stuck queues
Stuck queues are usually a design choice, not an accident. A queue with a release rate set too low will look stuck, because it is releasing people so slowly that no one's number changes in the time they are watching. A queue that holds inventory for people who have not checked out yet will look stuck, because the people at the front are holding items and the people behind them cannot move until the holds expire.
Ticketmaster gives buyers 10 minutes to hold items and check out once their turn comes. That hold is the bottleneck. If the people at the front take the full 10 minutes, or abandon their carts without releasing the hold, the queue behind them does not move for 10 minutes at a time. The queue is working as designed. The design is slow.
The fix is to make the queue transparent. Show the release rate. Show how many people are ahead of you and how fast they are moving. Show an estimated wait time that updates. A queue that shows its work is a queue people trust, even when it is slow. A queue that shows a number that never changes is a queue people assume is broken, and they are usually right.
What to do when it happens to you
If your queue is stuck, do not refresh. Leave the page open, check the event's status page, and wait 20 minutes. If the number has not moved in 20 minutes and the sale is live, the queue is stuck, and your options are to keep waiting or to try a different device or network, which starts you at the back of the line.
For the next sale, join the queue from the page the operator tells you to join from, not from a link you found elsewhere. Joining after the sale starts usually puts you at the back of the line, and joining from the wrong page can put you in a queue that is not the real one. The queue is a system with rules, and the rules are written on the operator's page, not on the resale sites.
Keep reading
Related guides on this site: what support queues look like after the sale how a queue becomes a sales channel how to load-test a queue before the drop More from Bot Protection For Ticketing.
Frequently asked questions
Why does my queue position never change?
It usually means the queue is not releasing people, or it is releasing them so slowly that your position does not change. The cause is often a bottleneck downstream: the checkout is slow, the inventory is held, or the release rate was set too low.
Does joining a queue early get me a better position?
Most waiting rooms assign your position randomly when you join, or when the sale starts. Joining early does not always help. Ticketmaster's pre-queue, for example, assigns positions randomly when the sale starts, so the people who joined first and the people who joined last have the same chance.
Should I refresh the page if my queue is stuck?
No. Refreshing usually sends you to the back of the line, or starts a new session that the system treats as a new joiner. Ticketmaster's help pages say explicitly not to refresh, and to keep the page open once you are in.
How long do I have once my turn comes?
Once your turn comes, most systems give you a limited time to complete the purchase. Ticketmaster gives you 10 minutes to hold your items and check out. If you do not finish in that time, your place is released to the next person.
How do I know if a queue is stuck or just slow?
The first sign is that the position number never moves while the sale is clearly happening. The second is that the page shows no activity, no timer, no updates. If the sale is live and your number has not moved in 20 minutes, the queue is stuck, not slow.
What should I do if my queue is stuck?
Leave the page open and wait, and check the event's social media or status page for a notice. If the queue is genuinely stuck, the operator will usually post about it. If there is no notice and the number still does not move, the queue is broken and waiting will not fix it.