FYI: We don't support listifications.app (in a dev sense), so we are not currently able to prioritize the fixing of a bug that only affects users of that tool. Please take up your concerns with the maintainer of that app.

Hmm, is this the bug where users are added/removed to the same list over and over again? Anyway, that's totally fair, but I'm curious why your tool does this.

So when we see something on the firehose that triggers automation, we don’t check each repo to confirm it hasn’t been labeled already, we just make the call to emitEvent#modEventLabel. Ozone issues the label over the firehose, regardless of whether a repo or post is already labeled.

This means it gets picked up by the tooling to add an account to the list whenever that tool sees the label event in the firehose.

I’ve been put on one too but I have no idea why or which one.