Why my automation didn't fire

Work through these in order. The run history on the automation itself tells you whether it fired at all, which splits the list in half immediately.

It never fired

Is it active? A draft or paused automation does nothing. This is the answer more often than anything else on this page.

Is it watching the right post? A comment-to-DM automation is armed against specific posts. A comment on a different post does not trigger it.

Does the comment actually contain the keyword? Matching is on the keyword appearing in the comment. Check for typos, and check you have not chosen a keyword people type in a different form.

Is the account connected? An automation on a disconnected account receives no events. See Connected accounts.

Is the suite on your plan? The automation suite is a paid feature. See when you hit a limit.

It fired but nothing was sent

Now you are looking at the compliance gates, and the run will say which one stopped it.

The messaging window had closed. Platforms allow a reply only within a window after the person contacted you. This is the most common block and it cannot be configured around.

That platform prohibits this kind of automated send. LinkedIn, for instance, does not permit automated DMs at all, so a send-DM action there is refused.

The person opted out. They are not messaged again. This is absolute.

It was paced. A burst is drained rather than sent at once; the message may simply not have gone yet.

All of these are explained in staying inside platform rules, and counted in automation analytics.

It sent the wrong thing

Check the flow in a dry run. A branch taken unexpectedly is nearly always a condition reading a tag that was never set. See contacts.

It is not on the screen you expected

On TrendSuite Lite the automation surface is Auto reply rather than the builder. See which edition you are on.