The most common cause is message access being switched off in Instagram's own settings, which lets the connection complete but stops delivery. After that: an expired token, the automation not attached to the post, a keyword mismatch, the person having restricted message requests, or the 24-hour messaging window having closed. Work through them in that order — it is roughly the order of how often each turns out to be the real problem.
Comment-to-DM automations fail quietly. Nothing errors, no alert fires, and you find out because someone comments asking why they never got the link. The causes are a short list, but they are not the ones most people check first.
Tadlo is built on Instagram Login and needs no Facebook Page — unlike ReplyRush, CreatorFlow and LinkDM, which all require one. That removes an entire account from the chain that can break your automation.
1. Message access is off in Instagram
The single most common cause, and the least obvious, because the connection in your automation tool looks completely healthy.
In Instagram: Settings → Messages and story replies → Message controls → Connected tools → allow access to messages.
If this is off, your tool authenticates fine, shows your account as connected, receives the comment webhook, and then cannot deliver. Everything looks right except the outcome.
This also switches itself off sometimes — after certain account changes, after switching account types, or occasionally after an app update. If your automation worked last month and does not now and nothing else changed, check this first.
2. The token expired or the connection dropped
Access tokens have a lifetime and get invalidated by things that seem unrelated: a password change, a session revoke, a switch between Business and Creator, a Meta security event.
Most tools show a stale "connected" state until they next try to use the token and fail. Disconnect and reconnect your account rather than trusting the status indicator.
If you are on a tool that authenticates through a linked Facebook Page, there is a second thing in the chain: a Page that gets unpublished, restricted, or loses its admin will break Instagram automation even though nothing happened to your Instagram account. That is the Facebook Page dependency, and it is invisible until it bites. Tools on Instagram Business Login, Tadlo included, have no Facebook account in the chain at all — which removes this entire cause rather than helping you diagnose it.
3. The automation is not attached to that post
Embarrassing and extremely common, particularly if you set the automation up after publishing.
Check whether it is scoped to a specific post, to your next post, or to all posts. "Next post" automations are the usual culprit: you create one, publish two posts, and it attached to the first.
If you promise a keyword in a caption, attach the automation before you publish. The first hour of a Reel is when the comments arrive fastest, and a gap there is unrecoverable — those people are not coming back.
4. The keyword does not match what people typed
Three separate failure modes hide here.
Substring matching. Does your tool fire on "GUIDE please 🙌", or only on a comment that is exactly "GUIDE"? If it requires an exact match, most of your real comments will miss, because people add words.
Case sensitivity. Most tools match case-insensitively. Confirm yours does rather than assuming.
Different word in different places. If you said "comment GUIDE" in the video and wrote "comment LINK" in the caption, you will get both and only one fires.
Look at the comments that failed and read what people actually typed. The answer is usually visible immediately.
5. The person's settings block it
Some people cannot receive your automated DM regardless of what you do:
- They have restricted message requests from people they do not follow.
- They have blocked or restricted you.
- Their account is set up in a way that does not accept message requests from businesses.
Nothing to fix here. If a small share of comments never convert, this is part of the reason and it is not a bug in your setup.
6. The messaging window closed
This affects follow-ups rather than the first message.
A comment does not open a 24-hour window. It entitles you to exactly one private reply, which Meta allows for up to 7 days from the comment. That one message is all you get until the person answers it.
The 24-hour messaging window opens only when they reply. Until then, later messages in your sequence have nowhere to go — the automation looks like it stopped halfway through, because there was never a second slot to use.
This is a platform rule, not a tool limitation, and the practical fix is the same either way: make your first message invite a reply. End with a question rather than a full stop. Their answer is what opens the window everything else depends on.
7. Rate limiting during a spike
If a Reel takes off and thousands of comments arrive in an hour, messages queue. Compliant tools pace delivery inside Meta's limits rather than firing in bursts, so during a spike some DMs arrive minutes later rather than seconds.
Delayed is not the same as failed. Check whether the messages eventually sent before assuming they were dropped.
8. The account type changed
Someone switched the account from Business to Creator, or back, or briefly to Personal. Any of these can invalidate the connection. Personal accounts cannot use the Messaging API at all, so if the account is currently Personal, nothing in the category will work until it is switched back.
A diagnostic order that saves time
- Comment the keyword yourself, from a second account that does not follow you. This tests the whole path including the follow gate. Testing from your own account often will not work at all.
- If nothing arrives — check message access (cause 1), then reconnect the account (cause 2).
- If your test works but real comments do not — the problem is keyword matching (cause 4) or post attachment (cause 3). Read the comments that failed.
- If the first message sends but follow-ups do not — the window closed (cause 6).
- If most send and a minority never do — recipient settings (cause 5). Not fixable.
Whatever tool you are on, its logs should tell you whether the comment was received and whether a send was attempted. Those two facts separate "the trigger did not fire" from "the trigger fired and delivery failed", which are completely different problems.
If your tool cannot tell you which of those happened, you are debugging blind, and that is a reason to change tools rather than a reason to keep guessing. Tadlo records every trigger and every delivery attempt against the flow in analytics, including the follow-gate outcome per person, so the answer takes one look rather than an afternoon.
What is not the cause
Two things people blame that usually are not it:
"Instagram is throttling my account." Occasionally true, usually not. Work through the list above first; in nearly every case the cause is a setting rather than an enforcement action.
"The tool is broken." Sometimes true. But if it worked before and nothing about the tool changed, something about the connection did — and causes 1, 2 and 8 are all changes on Instagram's side that produce exactly this symptom.
And if you have worked through this list because your current tool keeps failing quietly, that is worth weighing on its own. Tadlo runs on Instagram Business Login rather than a linked Facebook Page, which removes causes 2 and 8 from this list entirely — there is no second account in the chain to break. Comment-to-DM automation is on the free plan with unlimited DMs, so testing it against your current setup costs nothing. The setup guide takes about two minutes.
Frequently asked questions
Why is my Instagram comment-to-DM automation not sending?
Most often because message access is switched off in Instagram's own settings, under Messages and story replies, then Message controls, then Connected tools. This lets the connection complete and the comment webhook arrive while blocking delivery, so the tool appears healthy. Other frequent causes are an expired token, the automation not being attached to that specific post, and a keyword mismatch.
Why did my Instagram automation stop working suddenly?
Something about the connection changed even if nothing about the tool did. Access tokens are invalidated by password changes, session revokes and account-type switches. Message access can switch itself off after account changes. And on tools that authenticate through a linked Facebook Page, a Page becoming unpublished or restricted breaks Instagram automation even though the Instagram account is fine.
Why do some people get the DM and others do not?
Usually recipient settings. Some accounts restrict message requests from people they do not follow or from businesses, and those people cannot receive an automated DM regardless of your setup. The other common explanation is keyword matching — if the tool requires an exact match, comments with extra words around the keyword will not fire.
Why did the first DM send but not the follow-up?
Because a comment only ever buys one message. Meta lets a tool send exactly one private reply per comment, within 7 days of it — and the 24-hour messaging window opens only once the person replies to that message. If they never answered, there was no window for the follow-up to use. This is a Meta platform rule rather than a tool limitation. Ending the first message with a question is what makes the rest of the sequence possible.
Can I test my own comment-to-DM automation?
Test from a second account rather than your own, ideally one that does not follow you so the follow-gate path is exercised too. Commenting from the account that owns the automation frequently will not trigger a deliverable message, so a failed self-test does not tell you the automation is broken.
Are delayed DMs during a viral post a failure?
No. Tools running on the official API pace delivery within safe sending limits rather than firing in bursts, so during a large comment spike messages queue and go out steadily. Check whether they eventually sent before concluding they were dropped.
Does comment-to-DM work on a Personal Instagram account?
No. Meta's Messaging API only supports Business and Creator accounts, so no tool in the category works with a Personal account. If the account was recently switched to Personal, that alone will stop every automation until it is switched back.