It happens occasionally that what seems (to me, the flagger) a straightforward and basically undisputable flag is declined or disputed by a mod.
Reading through some of the related posts, I see that if one flag on a post is disputed, all flags on that post are automatically disputed, which might of course indicate that my flag was never even reviewed, but someone else (probably incorrectly) flagged the same answer, and their flag was disputed. (This seems to me a completely nonsensical way of managing flag disputes, but that’s not what this is about.)
With actual declined flags, though, there is no such ambiguity: someone definitely reviewed my flag and declined it. Now, this in itself is not a problem—it’s how the modding system is supposed to work—but occasionally, the decline just seems to be incorrect.
Most flags I submit are “Not an answer”; so too the one that sparked my writing here. In this question, which asks about the etymology of the suffix -th used to make abstract nouns from adjectives, a user posted this answer dealing with the old third-person verbal ending -th. In my book, that is absolutely not an answer: it is completely unrelated to the matter asked in the question.
Yet the flag was declined with what I am assuming is a standard option: “flags should not be used to indicate technical inaccuracies, or an altogether wrong answer”.
I presume simply flagging the same answer again would likely not help; but is there a ‘proper’ procedure to follow if I want to somehow express that I find the flag review incorrect?