Skip to content

Backtrack Comments in an Automation

3 min readUpdated

An automation only sees comments posted after you publish it. So the usual story goes: a reel does numbers overnight, you set up an automation the next morning, and the two hundred comments that arrived while you were asleep sit there unanswered forever.

Backtracking fixes exactly that. It runs a published automation back over comments that are already on the post, up to 7 days old, and replies to the ones that match its trigger.

Before you begin

  1. Open Automations in the console.
  2. Find the automation in the list and click the ··· menu at the end of its row.
  3. Choose Backtrack comments.
Backtracking lives in the row menu, not in the automation editor
  1. The Backtrack comments dialog opens. Click Backtrack Now.
The button spins while the run works through the post's comment history
  1. Leave the dialog open until it finishes. It reports Status: Completed along with how many comments the run processed, and the time of the last backtrack.
A finished run: 50 comments processed, and the automation's Hits count in the list behind it has moved

Processed comments is how many comments the run looked at — the whole eligible history on the post, not the number of replies it sent.

To see how many actually matched, look at the Hits column for that automation back in the list. In the run above, 50 comments were processed and the automation picked up 4 hits: the other 46 didn’t match its trigger and were left alone, exactly as they would have been live.

Then check the post itself. Backtracked replies appear threaded under the original comment, however old it is — a comment from five days ago picks up its reply in the same place a live one would, rather than as a new comment at the bottom of the post.

That’s worth knowing before you run it: the replies land deep in the thread where they make sense in context, not stacked at the end where they’d read as a burst.

Backtracking doesn’t reply to everything it finds — it re-runs the automation’s own trigger over the old comments. Whatever the automation would have done live, it does now.

That includes Intent Match. The automation in this run had no keyword at all — just the description when asked about delay — and the backtrack still found the comments that meant that and skipped the rest.

An intent match automation backtracks the same way a keyword one does
  • 7 days is a hard edge. Comments older than that are out of reach, whatever you do. If a post is about to age past the window, backtrack it now.
  • The automation has to be on. A draft or a switched-off automation has no trigger to run, so there’s nothing to backtrack with.
  • Your public reply limit still applies. Backtracked replies count toward the per-post cap like any other. On a post with a long comment history, that cap is what stops a single backtrack from filling the whole thread at once.
  • Run it once per post. Comments already answered are skipped, but a second run still walks the history and costs you the wait for nothing.

You should now have

A post that took off before your automation existed, answered anyway — every comment from the last 7 days checked against your trigger and replied to.

Next: Limit public replies on an automation