Why your Instagram DM automation stopped sending, and how to fix it
Short answer: Most stalled DM automations on Instagram (Meta's photo and video app) come down to four things: the 24-hour messaging window closed, the comment already got its one private reply, the monthly contact cap was reached, or the account login (token) expired. Blotato, a social media tool that posts to many platforms and can also send automated Instagram and Facebook direct messages (DMs), labels every run as running, waiting, completed, failed, expired or superseded. Read that label first, because each one points to a different fix.
Your comment-to-DM automation worked last week and now people comment the keyword and get nothing. Here is how to find out which of the usual causes you have, in the order that wastes the least time.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
A DM automation is a rule that sends a private message when someone comments a keyword on your post or messages your account. When it goes quiet, the cause is almost always one of a short list. This page walks through that list for Blotato's DM automations, using Blotato's own help pages and Meta's published rules. Meta is the company that owns Instagram and Facebook and sets the messaging rules that every tool must follow.
Blur Studio has not run these automations. Every fact below comes from the vendor's documentation, and vendor claims are labelled as such. The fix order at the end is a method you can run on your own account.
This page may contain affiliate links from which Blur Studio earns commissions.
First question: no runs, or failed runs?
Open the automation list and look at the numbers for each automation: Runs 24h, Success, Failed, Last run and State. Then ask one question. Did the comment start a run at all?
| What you see | What it means | Go to |
|---|---|---|
| 0 runs after a test comment | The automation never saw the comment, or the comment did not qualify | No runs checklist |
| Runs, shown as failed | The run started but Instagram or Blotato refused the send | The three common causes |
| Runs, shown as waiting | The run is paused on a follow or email gate, or a message is in flight | The six run states |
| Runs, shown as expired or superseded | The person never answered a gate, or a newer run replaced the old one | The six run states |
| Runs completed but the person says nothing arrived | The message may sit in Message Requests, or a desktop reader cannot see buttons | Sent but not seen |
The six run states, decoded
Blotato's API documentation lists six statuses for a run. A run is one trip through the automation for one comment or message. Here is what each means and what to do.
| State | Meaning (Blotato docs) | What to do |
|---|---|---|
| Running | The run is in progress | Wait a minute and refresh. A message that never settles within 30 minutes ends as expired |
| Waiting | The run is holding at a follow gate or email gate for the person's reply | Nothing is broken. The person must reply. Read the gate rules below |
| Completed | Every step finished | If the person still got nothing, check Message Requests and the button note below |
| Failed | A step was refused or errored. A webhook failure after the DM went out can also make a run fail | Open the run and read its error code and message |
| Expired | No answer inside the gate window: 30 days on a follow gate, 72 hours on an email gate | Expected behaviour. Shorten the gate message or drop the gate if many people stall |
| Superseded | A newer run started waiting on the same contact, so the older waiting run ended | Usually harmless. It happens when the same person is asked a gate question twice, for example after commenting the keyword a second time |
Blotato says expired and superseded runs count toward the started total but toward neither succeeded nor failed. A low success count with a low failed count often means people are stuck at a gate, not that something broke.
The three common causes of failed runs
Blotato's troubleshooting page names these first. The first two are Meta's rules, which no tool can work around. The third is Blotato's own plan limit.
1. The messaging window closed
Meta lets a business reply to a person only inside a window. For a normal message, the window lasts 24 hours from the person's last action. For a comment, you may send one private reply within 7 days of the comment, and you can keep talking only after the person answers, inside the next 24 hours. See my guide to the 24-hour messaging window for the full chain.
How it shows up: a failed run. In Blotato's messaging error list, "Message failed to send" (error code 20102) names the closed window as a common cause, so read the run's own error text to confirm. What to do: nothing can reopen a closed window from your side. If a gate is involved, remember that the 72-hour email wait and the 30-day follow wait are how long Blotato waits for the person. They are not Meta's send window. The docs say a message outside an allowed window fails, so treat late replies as likely to fail.
2. The comment already received its one private reply
Instagram allows one private reply per comment. If the comment already got a private reply from Blotato, from another DM tool or from you in the app, a second attempt is rejected. Blotato's docs say this holds through Blotato or another tool.
How it shows up: a failed run, often with the same 20102 error and the platform's reason in the message. It often appears after you test the same comment twice, after you edit an automation and republish while an old test comment is still on the post, or when two automations match the same comment. Blotato says that with two matching automations, one reply reaches the person and the other run fails. The fix is to keep one live automation per keyword on each account, and to test with a fresh comment each time.
3. The monthly contact cap was reached
Blotato counts active contacts: each person you message or reply to in a month. As of November 2026 the pricing page shows these monthly caps: Starter 1,000, Creator 6,000, Agency 15,000. When you reach the cap, a DM to a new person fails with error code 20101 and the run ends as failed. Blotato documents no overage purchase. You wait for the monthly reset or move up a plan. People you already counted this month can still be reached.
How to check: Blotato's Get Usage call in its API shows your current usage and limit, and the in-app chat can tell you if your account has a custom limit. If your failed runs began on the same day and affect only new people, suspect the cap. Replies you send through the inbox or API also count toward the same limit, so a busy comment-reply week can use up room you planned for DMs.
Other causes worth checking
The account login (token) expired
Blotato lists an expired connected account as a common cause. In the error list this appears as "The user has not authorized application" for Instagram and Facebook: the access token is no longer valid. Tokens go stale when they expire, when a password change revokes them, or when the Blotato app is removed from your Instagram's connected tools. Fix: open Accounts, reconnect the account and accept every permission. Blotato also says accounts connected before messaging, comments and follow gating launched must be reconnected.
An Instagram setting is off
In the Instagram app, open Settings, then Messages and story replies, then Connected tools, and make sure Allow access to messages is on. Then reconnect the account in Blotato and keep that option on when Instagram asks.
Another tool controls the conversation
If the first message arrives but the next one never does, another app may hold the conversation in Meta. Blotato's docs name ManyChat, a chatbot tool for Instagram and other channels, as a common source. Instagram handles the private reply to a comment separately, so the first message still lands, and Meta rejects the later one. Blotato's fix: in Meta Business Suite, open Conversation Routing, set the default routing app to Blotato or to none, and turn off Take control of conversations for every other app. Then republish and test from a different account.
The subscription is inactive
If the plan lapses, runs stop with error 20300 and new comments and messages start nothing. Blotato does not replay them after you reactivate, so comments left during the gap stay unanswered.
The webhook failed
A webhook is a web address Blotato calls after the message goes out, often to save a lead in a CRM, which is a customer database. A blocked, private or unresolvable address gives error 20304 and the run fails. A slow endpoint gives error 20305: Blotato waits 15 seconds, logs the timeout, and per the error page the run still completes. The statistics page says a webhook failure after a DM still makes a run fail. Those two statements differ, so open the run and read what it says for your case. Blotato does not retry a webhook, so a missed call stays missed.
The automation itself is invalid
Error 20303 means the automation is missing something: no active trigger, message text outside 1 to 640 characters, a button without a proper web address, a gate without a message, or a follow gate on a Facebook automation. Fix the field the error names and publish again.
Checklist when there are no runs at all
These come straight from Blotato's troubleshooting page. Work down the list and stop when something is wrong.
- The automation is Live, not Draft, and the trigger switch for comments is on.
- Your subscription is active.
- The comment contains one of your keywords. Matching ignores case and accents and matches anywhere in the word, so "price" matches "pricey". A photo, sticker or voice note never starts a run.
- The comment is a new top-level comment. A reply inside a comment thread does not start a run.
- The comment came from a different account. Your own comments never trigger.
- For a specific post, the comment is on the post you selected. The post picker lists only posts published through Blotato, and shows the 20 newest until you search by caption. For a post made in the Instagram app, use the "any post" option with a keyword.
- For a collab post, the automation sits on the account that published the post. A collaborator's automation does not fire.
- The account was reconnected after the messaging features launched, and the Instagram setting above is on.
If all eight pass and a fresh comment from another account still shows zero runs, Blotato says it is not receiving that account's comment events and you cannot fix it yourself. Ask support in the in-app chat, with the account handle and the automation ID.
Sent but not seen
- Buttons missing. Instagram shows message buttons in the mobile app only. A person on instagram.com sees the text with no buttons. Blotato's workaround is a plain-text URL in the message, but not alongside a button, because both together leave the link unclickable on desktop.
- Message Requests. Meta delivers a private reply to the Requests folder if the person does not follow the account. On Facebook, a Page message to someone who never messaged the Page may also land in Message Requests, and Blotato says it cannot change that. Use the public reply under the comment to tell people where to look.
The fix order I would use
- Open the failed run. Write down the state, error code, time and the commenter.
- Code 20101: check the contact cap. Code 20102: check the window and the one-reply rule. Code 20300: check billing. Code 20303: fix the automation. Codes 20304 and 20305: fix the webhook.
- Reconnect the Instagram account and confirm the Allow access to messages setting.
- Check Conversation Routing if only the second message fails.
- Make sure only one live automation matches each keyword.
- Test from a second account with a fresh top-level comment, never your own.
- Still stuck: contact support with the handle, the automation ID, the run time and the error text.
How to stop it happening again
- One live automation per keyword per account, and no second DM tool on the same account without Conversation Routing set.
- Watch the contact count by mid-month and plan the upgrade early.
- Reconnect accounts after any password change, and check the failed count weekly.
- Keep gate messages short and tell desktop readers to type a reply.
- Do not edit and republish a live automation in the middle of a campaign unless you have to. Each change is one more thing to check when runs fail.
A failure log you can copy
| Date and time | Automation | Commenter account | Run state | Error code and text | Likely cause | Fix tried | Result |
|---|---|---|---|---|---|---|---|
Send that table to support rather than a description.
When the tool is the wrong fit
If most of your failures are gates that nobody answers, or you need branching conversations, tags and several channels, a dedicated chatbot tool may suit you better. See ManyChat or Blotato for DMs. Blotato supports DM automation on Instagram and Facebook Pages only, so it will not cover TikTok, LinkedIn or WhatsApp. For the wider rules, read Instagram DM automation and spam and how Blotato DM automation works and where it stops.
How this page was checked
The facts come from Blotato's Help Center pages on DM automations, errors and billing, Blotato's pricing page, and Meta's developer pages on private replies and the messaging window. Last checked 21 November 2026, refreshed every 90 days. Blur Studio has not run Blotato itself. Test your own setup with the 7 day trial or an equivalent, and note that Blotato's pricing page and billing help page say the trial includes every feature except the API and MCP server, but its DM automation help page says only that automations are available on every paid plan, so Blotato does not spell it out. On day one of the trial, open the Automations screen and see whether it lets you create one. The pricing page shows caps of 1,000, 6,000 and 15,000 active contacts a month as of November 2026, and limits change.
How I'd approach this
Do not guess. In week one, build a failure log, open the failed run and match the error code to the list above. Read the code, fix one thing, retest with a fresh comment from a second account, and write down the result. If you have not signed up yet and want to see these run states yourself, you can look at Blotato's site and its 7 day trial, then build one test automation before you commit. If the issue is a bigger plan for how comments become customers, my free tools at /free or a free AI brainstorm call can help you decide what to automate and what a person should answer.
Questions people ask
Why did my Instagram DM automation stop sending?
The usual causes are a closed 24-hour window, a comment that already received its one private reply, a reached monthly contact cap, or an expired account login. Open the failed run, read its error code, and match it to the list on this page. Code 20101 is the cap and code 20102 is the window or one-reply rule.
What do the six Blotato run states mean?
Running is in progress. Waiting is paused on a follow or email gate. Completed means every step finished. Failed means a step was refused. Expired means nobody answered a gate in time, 30 days for follow and 72 hours for email. Superseded means a newer run on the same contact replaced it.
Can I send a second private reply to the same comment?
No. Instagram allows one private reply per comment, within 7 days of the comment, and Blotato's docs say a reply already sent through another tool also blocks it. After the person answers, you can follow up inside 24 hours.
What happens when I hit the active contact limit?
As of November 2026 the plan caps are 1,000, 6,000 and 15,000 contacts a month. A DM to a new person fails with error 20101 and the run ends as failed. Blotato documents no overage purchase, so you wait for the monthly reset or upgrade. Check the Blotato pricing page for current figures.
Why does the first DM arrive but the second never does?
Another app, often a chatbot tool such as ManyChat, may control the conversation in Meta. Set Conversation Routing in Meta Business Suite to Blotato or none, turn off Take control of conversations for other apps, republish and test again.
My own test comment does nothing. Is the automation broken?
Probably not. Your own comments never trigger an automation, and a reply inside a comment thread does not either. Test with a new top-level comment from a different account.
Does Blotato replay comments I missed while my plan was inactive?
No. While a subscription is inactive, new comments and messages start no run, and Blotato does not replay them after you reactivate. Reply to those people by hand.
Who do I contact when nothing here fixes it?
Use the in-app chat and include the account handle, the automation ID, the time of your test and the run's error text. For rule questions, see how Blotato DM automation works.
More in this topic: Social media: comment-to-DM and inbox automation (20 guides) →