No delay node in your automation doesn't mean messages send instantly or back-to-back. Several factors control when a task actually fires — here's what's likely causing the gap you're seeing.
Sender schedule window
This is the most common cause. Tasks only execute during the sender's active working hours. If a lead reaches a message node at 5 pm and the sender's schedule ends at 6 pm, the next task won't fire until the following working day — even with no delay node in the flow.
The same applies to weekends. If your sender is scheduled Monday–Friday and a lead reaches a node on Friday evening, the next message fires Monday morning.
How to check: Go to Sender Profiles → LinkedIn tab → Schedule and review the active days and hours. Also verify the sender's timezone — a wrong timezone shifts the entire window.
Daily limit and Auto-warmup pacing
GetSales caps how many tasks a sender executes per day via the Daily limit. Auto-warmup manages this limit automatically — it ramps up gradually toward your Target daily limit based on account age and health, and holds it there.
Once a sender reaches their daily cap, all remaining tasks for that day are pushed to the next working day. This means a lead that's "next in line" at 2 pm may not receive their message until tomorrow morning.
How to check: Go to the sender profile → LinkedIn tab → Auto Tasks & Daily Limits. Compare the Daily limit (actual today's cap) with the Done today count on the relevant activity card. If Done today = Daily limit, the sender is at capacity until tomorrow.
Warmer leads get scheduled first
GetSales prioritizes tasks based on where a lead sits in the automation flow: tasks from nodes closer to the end of the automation are scheduled before tasks from nodes closer to the start.
This is intentional. Leads further along in the flow have already engaged (accepted a connection, received earlier messages) — they're warmer, and it makes more sense to prioritize follow-up with them over firing the first touchpoint at newer leads.
In practice: if your sender has a daily limit of 50 messages and 200 leads are waiting across multiple nodes, leads at the later nodes in the flow will be scheduled first. Leads at the first message node may wait longer even though they "arrived" earlier.
Queue spread and dynamic updates
If many leads are waiting on the same node, GetSales distributes their tasks across multiple days according to the sender's daily limit. There's no way to send 500 messages in one day if the daily limit is 50 — leads further back in the queue simply wait their turn.
The queue is also dynamic — it updates in real time as events happen. When a lead finishes waiting on a timer node and moves to a Send Message node, they're added to the queue immediately. This means the schedule you see in the task modal can shift as new leads enter nodes throughout the day.
How to check: Click the In Progress counter on a message node → look at the scheduled dates in the modal. If tasks are spread over multiple future dates, that's queue pacing at work.
Timer node delays are a minimum, not a guarantee
If you've added a Timer node between messages (e.g. "wait 3 days"), that delay is the minimum gap — not the actual one. Here's what happens: once the timer expires, the lead moves to the next message node and enters the task queue. From there it still has to wait for the sender's working hours and available daily capacity, exactly like any other task.
So if your sender is already at their daily limit when a timer fires, or if many other leads are ahead in the queue, the actual gap between messages will be longer than the configured delay. A 3-day timer can easily result in a 4- or 5-day gap in practice.
This is expected behavior — the timer controls when the lead becomes eligible for the next message, not when the message is guaranteed to send.
In short
The gap between messages is almost always explained by one of these:
Cause | Where to look |
Outside sender working hours | Sender profile → Schedule |
Daily limit reached | Sender profile → Auto Tasks & Daily Limits |
Warmer leads scheduled ahead | Node modal → scheduled dates |
Many leads queued, spreading across days | Node modal → scheduled dates |
Timer node delay + queue wait stacking | Node modal → scheduled dates |
If you need messages to reach leads faster, the main lever is increasing the sender's Target daily limit (within safe Auto-warmup bounds) or adding more sender profiles to distribute the load.
Note: GetSales doesn't support scheduling a message for a specific date or time. There's no way to say "send this message on June 5th at 10 am." The system schedules tasks automatically based on the sender's working hours, daily limit, and queue order. The closest you can get is controlling the pace — by adjusting the Target daily limit or using a Timer node to introduce a fixed delay before the next step.
Related articles
• Auto-warmup Guide — how Daily limit vs. Target daily limit works and how Auto-warmup ramps output
• My Campaign Is Stuck — Troubleshooting Checklist — if tasks aren't firing at all rather than just delayed
• How to Check if Your Automation is Working — verify task execution at sender and campaign level