Skip to content

Comment Automation Not Working: The Comment Is Invalid for a Private Reply

Updated

Your automation is published, someone commented, and nothing was delivered. Instagram returned “the comment is invalid for a private reply”.

The message is Instagram’s, not LinktoDM’s. It means Instagram examined that specific comment and refused to let any app DM the person who wrote it.

There are four reasons, and they’re worth knowing apart because only two of them are fixable.

Reason Fixable?
The comment is more than 7 days old Only by acting sooner
A private reply was already sent to that comment No — and that’s correct behaviour
The comment was deleted between the trigger and the send No
The commenter’s privacy settings block message requests No, by anyone

Seven days is Instagram’s own limit on private replies, which is why backtrack also stops at seven days. A comment on a post that resurfaced weeks later can’t be answered by DM, however healthy your connection is.

A private reply is one-per-comment. If the person comments five times, only the first comment can carry the DM. This is also why One DM per user exists — without it, four of those five attempts are guaranteed failures.

Some people simply cannot be DM’d. Instagram lets users refuse message requests from accounts they don’t follow. When that’s on, no tool can reach them — LinktoDM, ManyChat or anything else. Some proportion of every audience is in this category, so a small number of these errors is normal rather than a fault.

The commenter's own setting, not yours. On Your followers or No one, no tool can reach them.
See Public reply sent but no DM for how to tell “normal” from “broken”.

One-off failures are the reasons above. Every comment failing is a different problem, and there are three to work through in order.

Expired or partial permissions are the single most common cause of a comment-to-DM automation that fires and then delivers nothing. Remove the app access and reconnect with every permission checked — Instagram automation not working has the steps.

Instagram hands messaging control to one app at a time. If ManyChat, AnyChat or any other DM tool is still connected, it holds thread ownership and your private replies fail even though the comment itself is perfectly valid.

Remove them from both places — Meta Business Suite and Instagram’s Apps and websites list. Removing from one side is not enough: Another app is controlling your conversations walks both.

This is worth doing even if you think you already did it. Apps connected during a trial months ago stay connected until you remove them.

An account switched back from Professional to Personal, or unlinked from its Facebook Page, loses messaging access entirely. See the Messaging API error for the eligibility checklist.

If permissions are fresh, no other app is connected, the account is eligible, and every comment still fails, the problem is on Meta’s side and LinktoDM can’t resolve it from here.

Report it through Meta’s Developer Bug Reports — the platform team reads these and they’re the only route to an account-level fix. Include:

  • Your Instagram professional account username
  • The error code and subcode Instagram returned, copied exactly
  • A timestamp for a specific failed attempt, with your timezone
  • The permalink of the post and, if you have it, the comment
  • What you’ve already ruled out — permissions refreshed, other apps removed, account eligible

Send the same details to LinktoDM support at support@linktodm.com and we’ll confirm what our side logged for those attempts, which is usually what Meta asks for next.