Yes, that would indeed the way to go.
A custom pipeline (reusing most of the default one). that applies this filtering for you.
The tricky thing is what to do when a server goes down, when the events are still in this ‘window’. These could potentially be lost.
That would be possible (solving it in the model), but will get messy quickly.
Is it imperative this is solved on the receiving side? Isn’t there a way this could be solved before the events are passed to Flowable?