Best answer
Set the post filter on the comment trigger. Without it the trigger listens to every comment on the account, which is exactly what you are seeing.
The filter takes the post the automation should watch, and everything else is ignored at match time rather than replied to and then regretted.
While you are in there, two related settings usually need fixing at the same time:
- The keyword mode. A launch word like DROP set to contains will match "dropped", "backdrop" and "drop me a line". Equals is the right mode for a word you told people to type exactly. Five modes are available and none of them guess, so the mode you pick is the behaviour you get.
- Priority. If you have several comment automations, the one that matches the longest keyword wins, so a generic catch all can quietly outrank a specific launch automation. Check the order before you assume the specific one is broken.
A pattern worth copying for launches: build one automation per campaign rather than one automation with growing keyword lists. It is easier to turn off, easier to measure, and it never inherits a keyword from something you ran last spring.
The Build and publish an automation article covers where the post filter and the match mode sit in the builder, and what changes the moment you publish rather than save.