DMs Are Very Slow to Arrive
Slow delivery is usually the system working, not failing. Before treating it as a fault, it’s worth knowing which of the two you’re looking at.
First, read the queue
Section titled “First, read the queue”Open the In queue panel in the console. It shows how many DMs and follow-ups are waiting and the rate they’re going out at — check your DM queue status explains how to read it.
| What the panel shows | What it means |
|---|---|
| A high count that’s falling | Working through a spike. Leave it |
| A count that’s flat or rising for hours | Arrivals are outpacing sending — see below |
| Zero waiting, but DMs still slow | Not a queue problem. Skip to the last section |
Why the queue slows down deliberately
Section titled “Why the queue slows down deliberately”Instagram caps private replies at 750 per hour per professional account, and caps overall API activity on a 24-hour rolling budget scaled by your impressions. A post that produces two thousand qualifying comments in an hour is over that line no matter how the sending is spaced.
LinktoDM’s Smart Queue Control watches how Instagram responds and eases off when it sees rate limiting, then picks the pace back up. A queue that drains slowly during a spike is the system choosing delivery over speed: the messages still arrive, later than they would have. Pushing harder gets them rejected instead.
There is no setting to raise the rate, no priority lane, and no plan that buys more of it — the limits are Instagram’s and apply to every tool. Rate limits and throttling has the full picture.
When a large queue is a problem
Section titled “When a large queue is a problem”It’s stale. Messages queued during a spike keep their place, but a DM answering a comment from six hours ago can land oddly. If the backlog has passed the point of being useful, clear the queue rather than delivering it — and switch the automation off first, or it refills.
It never drains. A count that’s been flat for hours with nothing going out usually isn’t throttling — it’s a broken connection. Check permissions, a password change, and message access.
You backtracked a big post. Backtracking a week of comments dumps the lot into the queue at once, against the same hourly ceiling as live traffic. Expect hours, and expect it to compete with new comments arriving.
When the queue is empty and DMs are still slow
Section titled “When the queue is empty and DMs are still slow”The delay isn’t in sending, so look at the automation itself:
- A delay step you set and forgot — check the automation for one before assuming a fault.
- A follow-up waiting on a condition. Follow-ups are counted separately from DMs in the queue panel for exactly this reason.
- An opener message — the real content doesn’t send until the recipient taps the button, so “slow” here is the recipient, not the system.
- It arrived on time, in Message requests, and was seen hours later.