An automation that stops working is worse than one you never set up. Customers keep messaging, expect the instant answer they got last week, and get silence – usually without anyone on your side noticing for days.
The frustrating part is that most failures are not bugs. They are rules: a keyword that has to match exactly, a connection that lapses after sixty days, a window that closes twenty-four hours after the customer’s last message. Each is documented somewhere by Meta; almost none are shown to you when they bite.
This guide starts by working out which kind of automation failed, because the causes are different for each, then walks through the checks in the order worth doing them. It is part of our wider look at DM marketing.
Key Takeaways
First, Work Out Which Kind of Automation Failed
Instagram DM automation comes in three forms, and the first question is which one you are using. The first is Meta’s own: the Inbox automations in Meta Business Suite, such as instant replies, away messages, FAQs and keyword replies. They run inside Meta and fail because of their own rules.
The second is a third-party tool – a chatbot builder, a CRM, or a Make, Zapier or n8n flow – connected through Meta’s official Messaging API. These fail when a permission, a connection or a timing rule gets in the way. Our guide to Instagram’s built-in auto replies covers the first kind in more depth.
The third is an unofficial bot that asks for your Instagram password and logs in as you. That is not a setting that has gone wrong; the method itself is the problem, and the section near the end explains why.
Symptom to Likely Cause
Match what you are seeing to the most likely cause, then jump to the section that fixes it.
| What you see | Most likely cause |
|---|---|
| A keyword reply never sends | The message did not match the keyword exactly, including capitals |
| A keyword reply sends late | Business Suite waits 15 minutes for you to reply first |
| The away message sent instead of the keyword reply | Template automations take priority over keyword ones |
| Instant and away replies stopped suddenly | Meta Business Agent was switched on, which pauses them |
| A third-party tool is connected but nothing sends | Allow access to messages is off under Connected tools |
| It worked for weeks, then stopped | The tool’s connection to Instagram lapsed; reconnect it |
| First replies work, follow-ups fail | The 24-hour messaging window has closed |
| Comment triggers never fire | The account is private, or the app lacks Advanced Access |
| Some automations are missing entirely | Regional privacy rules in Europe and Japan |
Business Suite Automations: Rules That Look Like Bugs
Keyword automations cause the most confusion. Meta’s own page on Inbox automations spells out the rules: each automation takes up to five keywords or phrases, keywords are case-sensitive, and a reply is not sent unless the keyword matches exactly. The same keyword can only be used in one automation. So a reply set for Price will not answer price, and nothing warns you.
Timing is the next surprise. Meta says a keyword automation is sent after 15 minutes unless you personally respond before then – so if you are active in the inbox, it may never send at all, which is by design. Keyword automations can also only be created on Business Suite desktop.
Then priority. When a template automation such as the away message and a keyword automation both match, Meta sends the template one and drops the keyword reply. And switching on Meta Business Agent pauses existing automations like away messages and instant replies. The scheduling side of that is covered in our guide to the Instagram away message.
Third-Party Tools: The Checks, in Order
For anything connected through Meta’s API, work down this list. Each step rules out the most common remaining cause.
Confirm a professional account
The Messaging API only works with Instagram professional accounts, business or creator. A personal account cannot be connected at all.
Turn on Allow access to messages
In the Instagram app: Settings, Messages and story replies, Message controls, Connected tools, then switch on Allow access to messages. Meta requires this for any tool to manage your messages.
Reconnect the account in the tool
Connections run on access tokens. Meta’s long-lived tokens last 60 days and have to be refreshed before they expire; if a refresh was missed, reconnecting issues a fresh one.
Check the timing of the message
Automated replies have to go out within 24 hours of the person’s last message. Anything later fails, however well the flow is built.
Make the account public for comment triggers
Meta only sends comment and mention notifications for public professional accounts – a private account leaves comment automations silent.
If you built the app yourself, check its access
Standard Access covers accounts you own or manage. Serving anyone else needs Advanced Access, which requires App Review and Business Verification, and the app must be set to Live for webhooks to arrive.
The 24-Hour Window Stops Most Follow-Ups
Meta’s Messaging API documentation gives a business 24 hours to respond to any message a person sends. Every new message from them reopens the window; silence closes it. That is why a welcome reply works perfectly while a follow-up scheduled for three days later fails without an error anyone sees.
There is one extension, and it is not for automation. The human agent tag lets a real person reply within seven days of the person’s message, for cases like a weekend closure or an issue that takes longer to resolve. It cannot be used to stretch an automated sequence.
The practical fix is design rather than settings: put the important information in the first reply, and give people a reason to reply back so the window stays open. The full set of what the API allows is in our guide to the Instagram DM API.
Comment Automations That Stop Firing
Comment-to-DM flows depend on Meta telling the tool that a comment arrived, and Meta’s webhook documentation sets two conditions: the account that owns the post must be public, and apps need Advanced Access to receive comment notifications at all. An account that switched to private for a week will find its comment automations quietly stopped.
The reply itself has limits too. A private reply can be sent once per comment, and only within seven days of it; after that the tool cannot message the commenter from that comment. Meta also caps private replies to post and reel comments at 750 an hour per account, which a big giveaway post can hit.
How the whole flow should be set up is covered in our guide to comment-to-DM automation.
Limits Worth Knowing Before Blaming the Tool
These are Meta’s published limits. When a tool hits one, the failure often looks like the tool’s fault.
| Limit | Value |
|---|---|
| Window to reply to a message | 24 hours from the person’s last message |
| Human agent tag (people only) | 7 days |
| Private reply to a comment | Once per comment, within 7 days |
| Private replies to post and reel comments | 750 per hour per account |
| Sending text, links, reactions, stickers | 100 calls per second per account |
| Sending audio or video | 10 calls per second per account |
| Long-lived access token | 60 days unless refreshed |
| Inactive message requests via the API | Not returned after 30 days |
When the rate limits in Meta’s rate-limiting guide are exceeded, calls fail with error code 80002 – worth knowing if your tool shows raw error codes.
When It Is Not the Automation at All
Sometimes the automation works and the message is simply somewhere you are not looking. Meta’s Inbox troubleshooting guide notes that messages in Instagram’s Hidden requests folder do not sync to the Business Suite Inbox until you move them to your main folder – our guide to Instagram message requests explains those folders.
If automated messages are going out and you do not know which system sent them, look at the end of the message: Business Suite automations say Sent by automated response. If it is not that, check ads that click to message, then any connected apps.
And if a manual message will not send either, the problem is not automation – it is the DM itself, covered in our guide to Instagram DMs not sending.
Tools That Ask for Your Password
Some automation services skip Meta’s API and ask for your Instagram username and password so they can log in as you. When these stop working, there is no setting to fix: the service is working against Instagram rather than through it.
Instagram’s help centre on third-party apps is direct about it – be careful before giving apps access to your account, and never share your login information with any person or app you do not trust. Official tools connect through Meta’s login screen and never need your password.
If the automation you rely on works this way, the fix is to move it to an official connection before it becomes an account problem rather than a messaging one.
Automation That Stays Working
Most of what breaks DM automation is plumbing: connections that lapse, windows that close, keywords that must match letter for letter. Every one of those is something a person has to notice and fix.
DMpro is built to keep answering. By its own description it replies to DMs, comments and mentions in your tone across six channels, understands the question rather than matching exact keywords, translates for 180+ languages, and hands the conversation to a person when it should.
- Understands questions instead of needing exact keywords
- Replies in your tone, not identical canned text
- Answers in the customer’s language, from 180+ supported
- Six channels answered from a single place
- A teammate can step into any conversation it is handling
- No case-sensitive keyword lists to maintain
- One place to see what was answered, and how
- Covers the hours nobody is watching the inbox
- Meta’s own rules, like the 24-hour window, still apply to every tool
Conclusion
When Instagram DM automation stops working, find the layer first. Business Suite automations fail on their own rules: exact, case-sensitive keywords, a 15-minute wait, template priority and Business Agent pauses.
Third-party tools fail on the plumbing: Allow access to messages switched off, a lapsed connection, the 24-hour window, or a private account silencing comment triggers.
Check those in order and most automations are running again within minutes – and if a tool needs your password, replace it rather than repair it.
Answers that understand the question, on six channels and in 180+ languages.
See how it works