kapacitor alert triggered by next alert

happened to me .I searched this problem here,it seems resolved two years algo .why it also happend.

this alert triggered by next altert.

if I set "where " node after "window" node ,it will triggered end of the period.

No source files, tests, or entry points are identified. Start by reproducing the reported task with a window node followed by a where node, and compare alert timing with and without that ordering. Done means the triggering behavior and end-of-period timing are explained and corrected, with the expected behavior confirmed.

Written by the indexing model from the issue text.