"When someone comments the keyword, absolutely nothing happens. No DM, no trigger, nothing." That's a real post from ManyChat's community forum, and if you searched your way here, it's probably your situation too. The frustrating truth about ManyChat automations "not working" is that there is no single cause: it's a stack of possible failures spread across your ManyChat config, your plan limits, your Instagram connection, and Meta's own rules, several of which fail silently by design. This guide covers all twelve real causes in triage order, with the exact fix steps for each, so you can stop guessing.
Quick note on what this article is: a consolidation of ManyChat's own help-center procedures, their staff's on-record statements, Meta's platform documentation, and the community threads where these failures actually get diagnosed. Sources are listed at the bottom. We build a competing tool, and this guide will still fix your ManyChat setup. Read to the end for the one honest paragraph about when switching makes sense.
Start here: the 60-second triage
- Is it everyone, or just you? Check status.manychat.com and skim the ManyChat community forum's recent posts. If dozens of people report dead automations on the same day, it's an incident: skip to fix #1 and stop changing your flows.
- Does the flow even run? Comment your own keyword from a second account. Nothing at all → connection or publish-state problem (fixes #2–#6). Works for you but not others → rules-and-limits problem (fixes #7–#10).
- Did anything change recently? Password change, new tool connected, Facebook Page reassigned, plan downgraded; each maps to a specific fix below.
1. Check whether it's an incident before touching anything
Platform incidents are real and bigger than your account. In January 2026, a ManyChat team member confirmed on the community forum: "We're currently aware of an ongoing incident on Meta's side that is affecting Instagram comment Automations on a large scale… it's not something we can directly fix in Manychat." Their recommended workaround during that incident: use Instagram DM keyword automations instead of comment triggers, because DM triggers kept working. A May 2025 thread describes the same shape: "my Instagram automations just… stopped. No replies to comments, no replies to DMs, no flows firing", with fifteen users confirming the same start date.
Fix: check status.manychat.com, then the community forum's newest threads. If it's an incident: don't rebuild your flows (you'll be debugging a moving target), switch comment triggers to DM keyword triggers where you can, and wait. Incidents get fixed; the flows you tore apart in a panic don't rebuild themselves.
2. Your automation isn't actually live
ManyChat's own troubleshooting doc lists this as cause number one for "automation not sent to contact": the flow isn't published. Drafts don't fire. Hitting "Set Live" also validates the flow and highlights broken pieces in red: unattached steps, missing attachments, and empty blocks all silently block publishing.
Fix: open the flow, press Set Live, and fix anything highlighted red. Then check the trigger itself; a keyword automation with a disabled trigger looks published and does nothing.
3. A Pro feature is hiding in your free-plan flow
On the free plan, a flow containing any paid-plan block refuses to publish. ManyChat's docs are direct about it: remove the blocks that contain paid features, or upgrade. This commonly bites people who build from templates: the template drops in a Pro block, and publishing fails with no obvious explanation.
Fix: walk the flow block by block and remove anything marked Pro, or upgrade. If you built from a template, suspect the template first.
4. You hit a plan limit and it looks exactly like a bug
This is the great impersonator. ManyChat's free plan covers 25 Active Contacts per month (not the 1,000 the older plan offered), and per a community moderator, free accounts max out at 3 keyword triggers: pressing Go Live on a fourth prompts an upgrade instead of publishing. An engaged account can consume 25 contacts within hours of a decent post, after which automation appears to simply stop. Nothing is broken; the meter ran out.
Fix: check your Active Contacts count against your plan tier in ManyChat's billing settings, and count your keyword triggers if you're on free. If you're consistently hitting the cap mid-month, that's a pricing decision, not a debugging one. Our ManyChat pricing breakdown covers what each tier actually includes.
5. Your Instagram connection broke (the password-change classic)
Changing your Instagram or Facebook password severs the connection, and everything stops. ManyChat's Refresh Permissions article says it plainly: log out of both ManyChat and your Instagram/Facebook account, log back in, then run Refresh Permissions again. The same article credits a permissions refresh with fixing failed sends, mismatched account info, comment-trigger issues, and default-reply problems. It's the closest thing ManyChat has to turn-it-off-and-on-again.
Fix: in ManyChat, use the Help button → "Refresh permissions" → choose Instagram and follow the prompts (or Settings → Instagram → Refresh Instagram Permissions). If it fails, do the full logout-of-everything cycle first, then refresh again.
6. The Instagram-side switches: account type and message access
Two settings on Instagram's side must be right or nothing works. First, the account must be a Professional account: Creator or Business; personal accounts can't connect. Second, the message-access toggle: in Instagram, Settings and activity → Messages and story replies → Message controls → Connected tools → enable "Allow access to messages." If that toggle is off, ManyChat can be perfectly configured and still completely deaf. And if you see a "Request Sent" button when connecting, the account is already linked to a different ManyChat workspace.
Fix: verify account type, flip the toggle, reconnect. If your Facebook Page was recently reassigned to the Instagram account, older connections (pre-June 2024 API) need ManyChat support to reconnect; that one isn't self-serve.
7. The once-per-user rule (it's not a bug)
ManyChat's help center documents this in black and white: the Instagram Post and Reel Comments trigger "only activates for the first comment a user leaves under a post or reel. If the same user comments again using the same keyword, the automation won't run a second time." ManyChat attributes it to Instagram API restrictions. So when a follower says "I commented twice and got nothing the second time," the system worked exactly as designed.
Fix: none needed, but design for it. Make the first DM count, and route repeat engagement through DM keywords (which a user can trigger fresh) rather than expecting comment triggers to re-fire.
8. The 24-hour window is silently eating your sends
Meta's rule: your app has 24 hours to respond to a user's message. ManyChat's docs add the part that surprises people: after the window closes, "you can continue to send manual messages via Inbox, but automations will no longer be delivered," and ManyChat "will automatically prevent those messages from being sent." Silent, by design. Delayed sequences and follow-ups aimed at contacts whose window closed simply don't go out. Manual replies from the Inbox get the human-agent allowance (up to 7 days), but that doesn't extend to automations, and on Instagram there's no message-tag escape hatch.
Fix: front-load your flow inside the interaction window. Anything you need delivered later must be re-triggered by a new user action (a fresh comment, story reply, or DM), not scheduled into the void.
9. Private-reply limits on comment-to-DM
Meta's private-replies documentation sets three ceilings people constantly mistake for breakage: replies can be sent within 7 days of the comment (so automations enabled after a post went viral can't reach older commenters), only ONE private message can be sent per commenter, and Live comments can only be answered during the broadcast. That one-message ceiling is why multi-message comment flows behave differently than DM-triggered flows.
Fix: put your link and value in the first message of any comment-triggered flow, and treat everything after as bonus that only fires if the user replies (which opens the messaging window properly).
10. The Requests folder problem: "my friends get it, strangers don't"
Meta's API docs state that conversations with followers land in Primary while non-followers' land in Requests, and the API gets no folder information. Put that next to the recurring community reports ("sends DMs to friends no problem… anyone else, it doesn't work") and the likely picture is that many "missing" DMs were delivered: into a folder the recipient never opens. To be precise: this causal link is a well-supported inference, not something either company documents outright.
Fix: you can't change where Instagram files the message. You can change the public reply to set expectations: "Sent! Check your message requests if you don't follow us." Small copy change, meaningful delivery-perception difference.
11. Two tools are fighting over your messages
Connect two automation tools to one account and Instagram hands conversations to one of them, often not the one you expect, with no error anywhere. ManyChat's docs cover assigning it as the primary receiver (Facebook Page settings → Advanced messaging → App settings → Instagram Receiver → Primary receiver), and their newer guidance steers users toward Conversation Routing instead of the old Handover Protocol entirely.
Fix: pick one DM automation tool per account. Disconnect trials you abandoned (Instagram: Settings → Security → Apps and Websites), then set ManyChat as primary receiver if anything else legitimately shares the account.
12. Keyword matching isn't doing what you think
Comment triggers match against include/exclude word lists, and the community threads are full of people whose keyword choice collides with normal conversation ("thanks" as a trigger fires on every polite comment; a keyword that appears in your caption can behave unexpectedly). Exact-match options exist for DM keywords but comment triggers are looser. One community-verified fix for a stubbornly dead trigger was simply attaching the automation to a different post — unglamorous, but it worked.
Fix: use distinctive trigger words (one word, unusual, uppercase in your CTA), check your exclude list isn't swallowing matches, and if a specific post's trigger is dead after everything else checks out, rebuild it against a fresh post.
When it's not fixable from your side
If you've walked all twelve and the automation is still dead: gather the flow link, the post link, a timestamped example of a comment that should have triggered, and your Refresh Permissions attempt, then open a ticket with ManyChat support. Free-plan users should know support queues are real; the community forum sometimes gets staff answers faster during incidents. And if the forum is full of people with your exact symptom and today's date, go back to fix #1: it's them, not you.
If you're debugging more than you're automating
Honesty section, as promised. Every tool on Instagram's official API lives under the same Meta rules you just read: the 24-hour window, once-per-comment, the Requests folder. Switching tools doesn't repeal Meta's physics. What differs between tools is everything else: how many failure modes the pricing model creates (flat-rate plans can't "run out" mid-month the way contact meters can), how triggers are structured, and whether you can reach a human when something breaks. InstantDM is our tool: $9.99/month flat with no per-contact billing, a free plan (500 automations/month) to test with, live chat support, and pacing safeguards on by default. If your ManyChat issues turned out to be plan-limit issues in a trench coat, the alternatives comparison is worth ten minutes. If they were config or Meta-rule issues: fix them here and carry the knowledge to whatever you run.
The verdict
ManyChat automation failures are rarely mysterious once you know the stack: incident → publish state → plan limits → connection → Instagram-side switches → Meta's silent rules (once-per-user, 24-hour window, one private reply, Requests folder) → tool conflicts → keyword hygiene. Triage in that order and you'll fix the majority of cases in under an hour, and know within five minutes when the honest answer is "wait out the incident." Bookmark this for the next time the DMs go quiet.
Sources and disclaimer
Official ManyChat documentation:
- Instagram automation troubleshooting (connection steps, primary receiver, message-access toggle)
- General automation troubleshooting (publish states, Pro-block limits, sequences)
- Refresh permissions
- Can't connect Instagram to ManyChat (account type, message-access toggle path)
- Instagram Post and Reel Comments trigger (once-per-user rule, post-type coverage)
- Understanding messaging windows (24-hour window, silent prevention of sends)
- Free plan (25 Active Contacts/month)
- Handover Protocol (primary receiver; Conversation Routing recommendation)
- ManyChat status page
Meta documentation:
- Instagram Messaging API (24-hour rule, Primary vs Requests folders)
- Private replies (7-day window, one message per commenter, Live limits)
Community threads quoted or referenced:
- "Manychat automation not responding to comments" (January 2026; staff confirmation of the Meta-side incident and the DM-trigger workaround)
- "URGENT: IG automation issue" (May 2025 incident thread)
- "Instagram automation not working" (partial-delivery complaints)
- "Comment to DM automation not working for most accounts"
- "IG automations not working" (May 2026)
- "Unable to create new automation on free plan" (moderator-confirmed 3-keyword cap)
Instagram features, ManyChat plans, and Meta policies change frequently; steps and limits are accurate as of July 2026. Community-reported figures (including any specific API rate-limit numbers circulating in forums) are not official Meta documentation and are excluded from this guide's claims.
ManyChat is a trademark of its owner. InstantDM is not affiliated with ManyChat; official documentation and public community threads are cited for troubleshooting guidance and commentary.
