[Bug] Alert triggering / Spam filtering

[brianleect]

Not sure if it's purely a coincidence due to differing "heartbeat" (Different second for program start).

Even if it differs slightly due to different start time, most updated version seems to consistently be seeing lesser notifications.

I suspect it might be due to how spam is being filtered for the latest version which filters out more alerts?

Will need more testing to confirm.

[itsXactlY]

Hey, same here somehow. Alerts getting double send for some weird reason.

Is there a way for a quick 'n dirty fix?

[brianleect]

Hey, same here somehow. Alerts getting double send for some weird reason.

Is there a way for a quick 'n dirty fix?

Don't think it's a case of double send in this case. You can see that one is triggered at 49m32s mark and the other at 51m1s mark.

Likely triggered due to high volatility as seen from a -34% to a -49% relative 1h change.

Not sure if this might be a network issue on your side as we should not be seeing such a significant delay from detection (49m,51m) of alert to sending message of over 5-6 minutes. (56m)

[itsXactlY]

Well, could being a API Limit. That bot was spamming >300 Messages/Minute. Need to finetune a bit as it seems like then.

[itsXactlY]

And me again, for some Reason the Bot stops suddenly, no clue why.