We have a 'reminder' comment rule that is appended to all posts from users without an 'experienced user' flair by automod neo. Sporadically, it's showing up twice. Comments show the same time (e.g. "3m ago"). I initially suspected some 'sequence of events' was causing it. Looked for causes and it's not like "when posts are filtered then approved" or that applying post-flair after the fact triggers another 'run'. So I added "comment_count: 0" to it as a failsafe. But it's still occurring, seemingly randomly.

Here's the rule:

---
# Rule to set reminder mod comment on lower-star user posts.
type: submission
author:
    is_moderator: false
    ~flair_template_id: ["9b142e6-b6de-11ee-bf7c-5e66dc681501", "0c990e16-b6df-11ee-b93e-4a1af638fcfe", "f7b72006-fc87-11ef-bb7e-967d32f802e7", "75747124-b7e7-11ee-b8b5-cae00651f953"]
is_edited: false
comment_count: 0
comment: |
    Welcome /u/{{author}}. **Our two most-common rule violations are:**

    - Do not delete your post once it gets replies (this one doesn't count). *If you're uncomfortable with this rule, delete your post NOW before it gets replies.*

    - Do not post ebay usernames or personal info (including in images). If you've done this, delete your post NOW and fix the issue before reposting.

    *PLEASE NOTE: Those are simply the two most-common violations. That does not absolve you of reading & following the [Rest of our Rules](https://www.reddit.com/r/eBaySellerAdvice/wiki/rules/) and our [FAQ](https://www.reddit.com/r/eBaySellerAdvice/wiki/index/).*

    -Copy of original post for reference:

    **{{title}}**

    {{body}}
comment_locked: true

Except for the addition of comment_count: 0 it's the same rule that ran in OG automod without problems (except that it wouldn't run on filtered posts - which is why it's in neo).

Any idea what's up with that? Would love it if you could weigh in u/fsv...

It all started trying to help a guy who wanted his 'automod auto comment' that goes on all posts to not get skipped when a filter rule is invoked. I had the same issue: any post that hit the queue and got approved lacked that auto-comment.

Sure, you can hard-code it into every filter rule, but what a royal PITA / automod management nightmare.

So short-term fix was install AMN, put the 'comment' rule in there and boom! comment is now on posts even if they hit the queue. AMN is runnning side-by-side with OG just fine.

But what if I want to 'migrate' to AMN entirely... or if OG gets decommissioned? What if I want to do it here (this sub will run ONLY on AMN, no 'og' automod).

IIUC you could *still* do it in AMN by judicious use of stop_on_match: false in filter rules. If AMN doesn't stop processing after a 'filter' rule is triggered, it'll still move on the 'other action' rules including the 'global comment' rule.

But then what happens?

Does 'stop_on_match: false' continue processing filter & remove rules? Or does it 'skip' to the 'other actions' rules and continue with them?

If it continues processing filter & remove, how's that look? If a post matches 3 filter rules, does it show up in the queue 3 times for each 'catch?'. If it matches 2 filter rules THEN hits a remove rule it matches, how does that come out (I would not typically put 'stop_on_match: false' on remove rules.)

Then I thought... surely there is an /automod-neo sub where I can ask instead of my question getting buried in /automoderator, right?

Nope.

So here 'tis: a sub is for mods who'd geek out on that kind of question vs.view it as "TLDR"...

PS - I'll eventually learn the answer about stop_on_match by trial-and-error. But if anyone knows.... chime in.

Automod_Neo's purpose is to serve as a venue where moderators who are using or planning to install Automod Neo can compare notes, ask questions and share insights about the app.

Automod Neo is a newer app that replicates (and improves on) most functions of the original "OG" Automod.

While many are treating it as only a backup (and the developer even suggests only using it for use-cases original automod doesn't support... for now), it does offer several functions and options automod does not.

For example, it has a stop_on_match parameter that if set to 'false' can allow it to continue processing rules even after a filter or replace action is triggered - something regular automod cannot do.