The send clear shouldn’t be a problem- with the “any change” flag, it actually just becomes a flag on the state. That is, there really isn’t any idea of “cleared” on an any change alert- the alert is both active and clear at the same time, because it changed. On analog alerts, you’re really just defining a window in which these on-change alerts are generated- it’s really not about being “active” in the window and “clear” outside of it, like it would be if “any change” was turned off.
Now, to the issue at hand- I can’t replicate the double alert. One thing that’s interesting to me is that the state you’re getting, 4369, means “REGISTER|ACTIVE|CLEARED|ACKNOWLEDGED”. It’s really the “register” part that’s interesting- it means this is coming from a change to the tag’s config. Once the tag is up and running, any changes inside your window should produce state “4368”, ie, no register. Do you still get two messages when this is the case?
Also, let’s look at one thing to narrow down from the start which side the problem is occurring on- the alert generation side, or the email side. Log into the gateway, and go to “Console”. Go to the “Levels” tab. Set the level for “Alerting.AlertBus” to “All”. Trigger an alert, and then go back and look at the console tab. You should see a message along the lines of “Alert published…” with the full info of the alert. Do you see one or two?