Turns out that the back-end could still send these events shortly after the guard was dropped.
Now using field is_dropped – which was designed for this, after all – to determine whether the guard has already been dropped, in which case we don't send the events.
Turns out that the back-end could still send these events shortly after the guard was dropped.
Now using field
is_dropped
– which was designed for this, after all – to determine whether the guard has already been dropped, in which case we don't send the events.