How to Fix Waalaxy Actions Stuck in the Queue (2026 Guide)
Queued is a normal state, not a failure. Four preconditions produce it, and the daily quota resets between midnight and 4am, so an afternoon queue often clears itself overnight without you touching anything.
The queue is full of pending actions and the dot is orange, not green. Nothing has gone out for hours. The campaign is not paused, there is no error, and the leads are sitting there waiting for something you cannot see.
Queued is a normal state in Waalaxy, not a failure, and that is the first thing worth knowing. The tool holds actions when a precondition is not met, and there are four ordinary preconditions. One of them, the daily quota, resets at a specific time most people do not know about, and it explains a large share of the queues that look permanent.
Why actions sit in the queue
Waalaxy queues an action when it is scheduled but not currently permitted. The reasons are all deliberate, which is why the interface does not treat any of them as an error. Knowing which one you have takes about a minute.
| Reason | How you recognise it | What to do |
|---|---|---|
| Daily quota reached | All similar actions delayed at once, part-way through the day | Nothing, it resets between midnight and 4am |
| Outside your working hours | The queue moves during the day and stops in the evening | Widen the schedule in Settings, Account activity |
| Cloud disconnected | Nothing runs at all, including inside working hours | Reconnect the Cloud, the connection cookie expires |
| A wait condition has not elapsed | Only part of the sequence is held, earlier steps went out | Nothing, or shorten the delay in the sequence |
| Computer off or no LinkedIn tab, on Freemium | Only affects free plans, nothing runs while you are away | Keep a LinkedIn tab open, or move to a paid plan |
The first row is the one that resolves the most cases and the one almost nobody knows: when you hit a daily quota, all similar actions in the queue are delayed until the next reset, and that reset happens daily between midnight and 4am. A queue that alarms you at 4pm is frequently a queue that will be gone by breakfast.
The Freemium distinction is worth stating plainly too, because it changes what a healthy setup looks like. On a paid subscription the Cloud runs your actions, so your machine can be off. On Freemium there is no Cloud: the computer needs to be on with a LinkedIn tab open, and closing the laptop stops the queue.
The four checks, in order
Cheapest first. Most queues are explained by the first two and need no action at all.
Check the time and your quota
If the queue built up part-way through the day and all the held actions are of the same type, you have hit that action's daily quota. The correct response is to do nothing: quotas reset between midnight and 4am and the queue drains on its own. Raising limits to force it through is the change most likely to cost you the account.
Check your activity schedule
Actions are postponed outside your working hours. Open Settings and Account activity to see the window you are actually running, which is often narrower than you remember setting. If your leads are in another timezone, widening it here is a legitimate fix rather than a workaround.
Check the Cloud connection
If nothing is running even inside working hours and under quota, look at the Cloud. It can disconnect on its own because the connection cookie expires, so a setup that worked last week can be silently disconnected today. Reconnect it and the queue starts moving within minutes.
Check the sequence conditions
If only part of the sequence is held while earlier steps went out, a wait condition has not elapsed. A rule like wait three days after the connection is accepted will hold everything behind it, correctly, until the delay passes. Shorten the delay only if the sequence genuinely does not need it.
Keep the queue moving
Four habits stop most queues from forming in the first place.
- Set the schedule to match your leads, not your own working day. If you prospect across timezones, a nine to five window in your timezone throws away half the sending capacity you are paying for.
- Check the Cloud connection weekly. The connection cookie expires on its own, and this is the failure that produces a complete stop rather than a partial one.
- Spread the campaign start times. Launching everything at once guarantees you hit the daily quota by mid-morning and spend the rest of the day queued.
- On Freemium, expect the constraint. No Cloud means the computer must be on and LinkedIn open, so an overnight queue is not a bug, it is the plan you are on.
None of that makes actions go out faster than LinkedIn allows. It removes the queues that come from your own configuration rather than from the limits, which is most of them.
If the extension is also failing on imports, that is a different failure with a different cause. We covered it in how to fix a Waalaxy lead import stuck at 0 percent.
Pipelines with no queue to watch
Step back and the queue is a scheduling problem: a fixed list of actions, waiting for a window in which they are allowed to happen. The tool holds them, you check on them, and the whole thing depends on a configuration you have to remember to keep right.
ReactIn's lists are not a fixed batch. People enter as signals fire and the campaign contacts them when it is their turn, so there is no backlog of pre-scheduled actions sitting behind a window. Sending runs on our servers, so nothing depends on your computer being on or a tab staying open, on any plan.
Campaign ponderation is the same idea applied to priority. When several campaigns want the same person, it decides who gets contacted first rather than letting a queue resolve it by accident of ordering.
The honest limit: LinkedIn's own daily limits apply to ReactIn exactly as they do to Waalaxy, and no tool sends more than the platform allows. What changes is that you are not managing a visible backlog and a schedule to feed it. If you run one account inside normal hours, Waalaxy's queue is not costing you anything and this is not an argument to switch.
For a feature-by-feature view of the two, see our ReactIn vs Waalaxy comparison.
The queue is usually the tool protecting you from something. Work out which of the four conditions is holding it and most of the time the correct action is to leave it alone.
Frequently Asked Questions
Sources & Further Reading
- Waalaxy explains the mechanism in how does the Waalaxy queue work.
- The quota and delay figures are in Waalaxy's delays and quotas guide, worth checking for the current numbers.
- For what the Cloud does and why it needs connecting, see Waalaxy runs itself thanks to the Waalaxy Cloud.
- And for sequence conditions specifically, what are the conditions in a Waalaxy campaign.
Related Articles
How to Fix Expandi Messages Not Sending (Pending Invites)
A connector campaign opens with a connection request, and a lead who already has one pending cannot receive a second. So the campaign has nothing it is allowed to do, and it says so in a tab most people never open.
How to Fix Phantombuster "Error During Loading of Chat Widget"
Phantombuster documents this one, and the documented fix is mostly to wait. The expensive part is a Phantom left looping against it, burning execution time on attempts that cannot succeed.
Working Around the Limitations on Salesflow (2026 Guide)
CSV import exists, so does a campaign type for contacts you already hold, and so do shared blacklists. The constraints that actually bite are narrower: rejected Sales Navigator URLs, per-route caps, and a deliberate block on duplicates.
How to Fix Dripify Lead Collection Stalls (2026 Guide)
Most stalled collections have finished or are waiting. The Lead Collection Report names the cause, the search cap ends runs silently, and working hours suspend lead loading as well as sending.