Everything here about how Instagram and Meta behave is true on any tool. The specific fix steps are labeled for ManyChat, since it's the most common comment-to-DM tool and the one most people are asking about. On a different platform like ChatGenius the platform rules are identical, the equivalent settings just live in your own flow builder.
Your automation is live, permissions are refreshed, the keyword is right, and the account is connected. Someone comments and nothing happens. No DM, no trigger, nothing. The good news: this is almost never your flow. It falls into two buckets, a silent config problem on your side, or a Meta-side issue that hits every automation tool at once.
1. The two silent config killers (a two-minute check)
Before anything else, rule these out. They quietly break Instagram automations and the dashboard gives you no warning:
- Professional account. The Instagram account has to be a Professional account (Creator or Business). A personal account cannot run automations.
- "Allow access to messages" must be ON. In the Instagram app: Settings and activity, then Messages and story replies, then Message controls, then Connected tools. A Meta app update flips this off silently, and your tool still shows "Connected" even when it is off. Comments come in, but no DM can go out until you flip it back on. This one trips up a huge number of people.
- Set Live. Open the automation and hit Set Live. New or recently-edited automations default to paused, and editing one can quietly toggle it back to Draft. (In ManyChat it's the red Set Live button; every tool has an equivalent.)
- Refresh Permissions. In ManyChat this is under the Help menu, and their own help text says to do it first when content stops sending. Other tools have a reconnect or refresh equivalent.
2. If config checks out, it's almost certainly Meta's side
If you have confirmed all of the above and it still fails, the problem is bigger than your setup. Instagram's comment webhook delivery from Meta has been running intermittently since late 2025, well below full uptime, and it affects every automation platform, not one tool. When the webhook event does not arrive, your trigger never sees the comment, so nothing fires. No tool can fully fix this on their end until Meta does.
There are real rate ceilings too (Meta documents a limit of 750 private replies per hour per account for comment-triggered DMs), but at normal volume the webhook delivery gap is the more common culprit right now, not the rate cap.
If your automation sends both a public comment reply and a DM, those are two separate Meta calls with separate subscriptions. They fail independently, and lately the public-reply call breaks first, which can silently halt the whole flow before the DM ever fires. Build a DM-only version with no public reply and test it. If the DM-only version works, your public-reply step was killing the flow.
3. The fix order that actually works
These use ManyChat's labels, since it's what most people are on (other tools have the same equivalents). Run them in order, and do not jump to the nuclear option:
- Hit Refresh Permissions, wait a few minutes.
- Post a test comment with your trigger word from a different account (not your own, see below).
- Still broken? Use Change Instagram Connection and reconnect via Meta for Business (the second option, not the direct Instagram OAuth). This forces a clean re-handshake and usually clears stuck webhooks.
- Last resort only: remove the Instagram account and add it back fresh. This does wipe your subscriber list, so only do it if steps 1 to 3 fail.
Do not rebuild your flows into a new setup. They live in your account, not on Meta, and they pick right back up once the connection is healthy again.
4. One more gotcha: once per user, per post
Comment triggers fire once per user per post. If you keep testing with the same account on the same post, it will only fire the first time, which makes it look broken when it is not. Always test with a fresh account.
The honest part
When it really is the Meta webhook outage, no tool escapes it, anyone telling you their platform is immune is not being straight with you. The practical fallback while Meta is flaky: a DM keyword trigger (someone DMs you a word) has been more reliable than comment triggers lately, so adding one as a backup catches people the comment trigger misses.
Stuck after all of this?
This is exactly the kind of thing where a real person who knows Meta's plumbing beats a help-desk script. ChatGenius is built and run by a small founder team, so when your automation breaks you reach someone who can actually look at what's failing and tell you whether it's your config or Meta. We run the same comment-to-DM + AI stack, so we've diagnosed this exact problem more times than we can count.
See how ChatGenius works Or start free and message us.Frequently asked questions
Almost never your flow. The two silent config causes: the account must be a Professional account, and "Allow access to messages" must be ON in the Instagram app (your tool shows Connected even when it's off). If config is fine, it's usually Meta's comment-webhook delivery, which has been intermittent since late 2025 across every platform.
Instagram app: Settings and activity, then Messages and story replies, then Message controls, then Connected tools. A Meta app update sometimes flips it off silently, and when it's off, comments come in but no DM goes out.
They're two separate Meta calls that fail independently. Lately the public-reply call breaks first and can silently halt the flow before the DM fires. Test a DM-only version with no public reply to isolate it.
1) Refresh Permissions. 2) Test from a different account. 3) Reconnect via Meta for Business (not direct IG OAuth) to force a clean re-handshake. 4) Last resort: remove and re-add the account (wipes subscribers). Don't rebuild flows, they resume on their own.
Usually nothing on your end. Meta pushes scope refreshes that silently break old connections, and its comment webhook has been below full uptime since late 2025. A reconnect via Meta for Business clears most of it. Also remember comment triggers fire once per user per post, so re-testing with the same account won't re-fire.