Instagram DM Automation Not Working? Common Problems and How to Fix Them

By the end of this guide, you'll know the most common technical reasons Instagram DM automation stops working, and how to check and fix each one — separate from copywriting or flow-design problems, this is about messages simply not sending at all.

Start by Confirming the Basics

Before troubleshooting anything more specific, a few foundational things are worth ruling out first, since they're the most common root causes:

1. Your Account Isn't a Business or Creator Account

DM automation only works on Instagram Business or Creator accounts connected to a Facebook Page — a personal account has no API access at all, and automation simply can't connect to it. If you're not sure your account is set up correctly, our guide on switching to a Business or Creator account covers the exact steps.

2. The Facebook Page Connection Has Broken

Instagram's API access runs through a linked Facebook Page. If that connection gets disconnected — sometimes silently, after a password change, a permissions review, or an unrelated Facebook account update — automation stops working even though nothing about your Instagram account itself changed. Reconnecting the Page in your Instagram settings usually resolves this.

3. Permissions Were Revoked

Automation runs on permissions you granted through Meta's official OAuth login. If those permissions get revoked — sometimes accidentally during a routine security review of connected apps — the automation tool loses access even though everything looks fine on the automation platform's side. Checking Instagram's connected apps list under Settings will show whether the connection is still active.

Reasons Specific Messages Aren't Sending

• Outside the 24-hour messaging window. Standard promotional messages can only be sent within 24 hours of someone's last interaction. A flow trying to send a follow-up outside that window using a standard message type will fail silently rather than send late.
• Hourly conversation limit reached. If your plan's conversation cap for the hour has been hit, new messages queue rather than send immediately — covered in more detail in our guide on handling traffic spikes. This isn't a failure, just a delay, but it can look like automation "isn't working" if you're expecting an instant reply during a high-volume moment.
• A deprecated message type is being used. Meta has retired several message tags over 2026 — a tool still referencing one of these will fail to send without necessarily throwing an obvious error, a specific risk covered in our guide on Meta's 2026 API changes.
• The triggering comment doesn't exactly match the keyword. Keyword matching is usually exact or close-match — a comment that says "whats the price" won't trigger a flow set to the keyword "PRICE" unless the flow is configured to catch variations.

Reasons a Flow Isn't Triggering at All

• The flow isn't attached to the post being commented on. A flow only fires on the specific post (or posts) it's configured for — a comment on an unrelated post won't trigger it, even with the right keyword.
• The flow is paused or disabled. It's an easy setting to overlook, especially after editing a flow — worth a quick check if triggers that used to work suddenly stop.
• You've hit your plan's active automation limit. Each plan tier has a cap on active automations — if you're at that limit, a newly built flow may not go live until an older one is paused or removed.

A Simple Troubleshooting Order

When something isn't working, check in this order: account type and Page connection first (the foundational layer), then permissions, then the specific flow's settings (is it active, is it attached to the right post, does the keyword match), then timing and volume limits last. Most issues resolve at the first or second step.

Next Step

If you've checked all of the above and something still isn't working, log into Maedix to review your flow settings directly, or reach out through support if the issue persists after a full check.