Instagram Auto DM Not Sending? (2026) — 8 Causes and the Order to Check Them
The automation is on, the comment came in, and no DM goes out. The most common mistake at this point is to toggle the tool off and on, tweak the keyword, and — when that fails — conclude that "the tool is broken." In reality, the causes are a mix of things on the Instagram account side, things on the tool settings side, and cases where the DM was sent but the recipient can't see it — and each one is checked in a different place. This post sorts the questions the UUP team has actually received while running DM automation by cause, into a checklist you can work through from the top down.
Checked as of September 2026. Instagram renames and moves its settings screens constantly, so details may differ. This post is written by the team that builds UUP.
First, split it up — "not sending" means three different things
The same report can mean any of three actual states. Which one it is completely changes where you look.
| State | The tool's send record | Where the cause lives |
|---|---|---|
| Never even attempted | No record | Tool settings (automation off, keyword, target post) or connection status |
| Attempted but rejected | A failure record exists | Instagram account settings, token, policy window |
| Sent but unseen | A success record exists | The recipient's side (requests folder, block) |
So step one is opening the tool's send status. UUP shows the send count per automation and the account's sending state (normal, queued, rate-limited, stopped), and notifies you of final failures. If the send count is 0, go to causes 1-4. If you got a failure notification, go to 5-7. If it sent but wasn't seen, go to 8.
Causes 1-4 — when nothing is even attempted
1. The automation isn't actually active
Saving a draft is not the same as activating. It's common to have scheduled activation set for a time that hasn't arrived yet, or a duplicated automation still sitting in draft. Check the status toggle in the list first.
2. The keyword or target post doesn't match
This is the "specific post" automation where the comment landed on a different post, or an exact-match keyword when the comment has extra spaces or emoji mixed in. When testing, comment from a different account — no DM is sent for a comment left by the account owner (there's no reason to send yourself a guide DM, and most official-API tools follow the same rule).
3. The connection dropped or the token expired
An Instagram connection token is valid for 60 days, and the tool refreshes it before expiry. But changing your password or tapping "Log out of all devices" on Instagram invalidates the token on the spot. The screen can still show "connected," which makes this the most confusing cause of all. When UUP detects an invalid token while loading your post list, it immediately drops the connection to reconnection required and shows a notice — if there's a reconnect button on the connection screen, this is your cause.
4. Your plan or billing status is blocking sends
DM automation is a paid feature. With UUP, the free and BASIC plans don't include DM automation; sends happen only on DM Pro, Ultra, and the 14-day trial. If the trial ended or a payment failed and sending stopped, the automation stays in the list but no DM goes out. Check the notice at the top of the dashboard and your current plan on the pricing screen.
Causes 5-7 — attempted, but Instagram rejected it
5. Message access for "Connected tools" is turned off in Instagram settings
This is the most frequently missed cause. In the Instagram app, under Settings → Messages and story replies → "Connected tools" (or connected apps in Accounts Center), if message access for the tool is off, Meta rejects the send no matter how healthy the tool is. The first time this rejection happens, UUP sends you a support team note with the exact settings path, and once you turn the setting back on it automatically resends the DMs that were waiting in the meantime. If you got that note, you don't need to touch the tool at all — just turn the Instagram setting back on.
6. More than 7 days have passed since the comment
Under Meta policy, a private reply (the first DM) to a comment on a post or Reel can be sent only once, within 7 days of the comment being created. Features that retroactively send in bulk to comments on older posts also only cover comments inside that 7-day window. Comments on live broadcasts work only during the broadcast. Follow-up messages after the first DM (cards, carousels) can only be sent inside the 24-hour window that opens once the recipient replies — if they don't reply, the follow-up not going out isn't a failure, it's expected.
7. The post was classified as restricted content, or you hit the hourly limit
Posts Meta has classified as age- or country-restricted, or as sensitive topics, are excluded from comment automation by external tools (other tools list the same item in their FAQs). And private replies have a documented limit of 750 per account per hour, so when a Reel blows up and comments flood in, anything over the limit isn't an immediate failure — it's queued and sent in sequence. UUP marks this state separately as "queued" — reading it as a failure and toggling the automation off and on doesn't affect sends already queued, but you'll miss any new comments left while it was off.
Cause 8 — it was sent, but the recipient never saw it
If the send went through and you still hear "I never got the DM," then when the recipient isn't a follower, that DM sits in the message requests folder rather than the inbox. Requests give weak notifications, and before the request is accepted, links in the message body aren't tappable. That's why UUP can send the first DM of an instant-send automation as a card with a link button (scheduled and batch sends go out as text) — the card's button is tappable even while it's sitting in requests. The full behavior is written up in the message requests post.
The check order, summarized
- Open the tool's send status — distinguish no attempt / failure notice / successful send.
- No attempt → is the automation active → keyword and post → connection status (reconnect notice) → plan.
- Failure → Instagram "Connected tools" message access → the 7-day comment window → restricted content or queued at the limit.
- Sent but unseen → explain the requests folder, switch the first DM to a card.
- If everything checks out and it still won't send, send your tool's support team the automation name, the comment timestamp, and the account that left the comment. Those three are what let them find the send record immediately.
Frequently asked questions
Does toggling the automation off and on fix it?
Not unless the cause is number 1 (active status). In particular, while you're queued at the limit (cause 7), toggling gains nothing — you'd only miss the new comments left while it was off.
If I reconnect, do I have to rebuild my automations?
With UUP, reconnecting the same Instagram account carries your existing automations over as-is. Note that disconnecting pauses the automations, so you'll need to switch the status toggle back on after reconnecting.
The first DM went out, but the product card doesn't
The card only goes out after the recipient replies. That's Meta's 24-hour window rule, and no tool can change it. If you need a product card in the first DM, use UUP's first-DM card (which includes a link button).
Related reading
- The Complete Guide to Instagram Auto DM — How It Works, Why Messages Fail, and Real-World Setup
- Instagram Message Requests, Explained — Why DMs Go Unseen
- Instagram DM Automation Without Getting Your Account Banned — The Official API and the 24-Hour Rule
If you want DM automation that tells you what's blocking it through notes and notifications, start free and check it out on the 14-day trial.