How the DM Queue Works

A message your automation sends doesn’t go out the instant its trigger matches. It goes into the DM queue first, and LinktoDM releases it from there at a rate Meta accepts. This page covers what happens to a message while it’s in the queue.

The trip a message makes

Every message takes the same four steps:

1. A trigger matches — someone comments, replies to a story, or a follow-up comes due.
2. LinktoDM builds the message and puts it in the queue.
3. The queue releases messages at a steady rate rather than all at once.
4. Each one goes out and leaves the count.

Under normal traffic the whole trip takes seconds, which is why the queue is usually invisible: the count sits at 0 because messages leave as fast as they arrive. It becomes visible only when messages arrive faster than the safe rate lets them leave — the moment a post spikes — and that is exactly when you want it there.

Two kinds of waiting

Not everything in the queue is waiting for the same reason, which is why the queue panel counts them separately.

• DMs are waiting on sending speed. They’re ready now; the queue is spacing them out. This is the number that moves during a spike.
• Follow-ups are waiting on time. A follow-up step or a delay told them to go out later, and they sit in the queue until their timer says otherwise. A follow-up scheduled for tomorrow is in the queue all day, and that’s the feature working.

What the queue guarantees

Nothing is dropped while it waits. A queued message is a message that will be sent, just not this second. It survives the wait, and the only things that remove it are being sent or being cleared by you.

It’s per account. The panel sits under the account switcher because the queue does too: every connected Instagram account or Facebook Page has its own, so a busy account and a quiet one don’t share a backlog.

The one thing the queue doesn’t do is go faster on request. There’s no priority lane and no setting to raise the rate; when Meta tightens, LinktoDM slows down deliberately so that the messages still get through.

Common questions

Does the queue delay every DM? Technically yes, in practice no. Every message passes through it, but under normal traffic it’s out again in seconds. The delay only becomes noticeable when a post generates messages faster than the safe rate can release them.

Why does my queue say 0 when an automation is live? Because it’s keeping up. A count of 0 is the normal state, not a sign that nothing is firing. To confirm an automation is running, use its Hits column in the Automations list.

Can I make it send faster? No, and that’s the point. The rate is set by what the platform will accept from your account at that moment, not by a plan or a setting. The lever you do have is upstream: send fewer messages by tightening the trigger or by running fewer automations on the same account at once.

Will a queued message expire if it waits too long? No. Waiting doesn’t discard a message. It leaves the queue by being sent or by being cleared by you, and nothing else.

A follow-up is scheduled for next week — does it sit in the queue that whole time? Yes, and that’s expected. Follow-ups wait on their timer rather than on sending speed, so a large Follow-ups count on an account running long delays is normal.

Do my accounts share one queue? No. Every connected account has its own queue and its own rate, so a launch on one account doesn’t slow the others down.

Does pausing the queue switch my automations off? No. Triggers keep matching and messages keep piling up behind the pause — they’re delayed, not cancelled. To stop sending for longer than a few minutes, switch the automation off instead.