Fix running state behavior with delete

[Marenz]

When a dispatch is deleted, the running state change notification telling the actor that it is no longer running will only be sent if there are no other dispatches of the same type running.

Signed-off-by: Mathias L. Baumann mathias.baumann@frequenz.com

[llucax]

So the previous behaviour was that a stop event was sent even when there were other dispatches running for this type, so the dispatch would have stopped when it shouldn't, right?

[llucax]

I would add documentation about what this is for, as it is not trivial to figure it out.

[Marenz]

So the previous behaviour was that a stop event was sent even when there were other dispatches running for this type, so the dispatch would have stopped when it shouldn't, right?

correct

[llucax]

I think we should not apply this, as if we need to be able to handle overlapping dispatches that have different parameters, we don't get notified when one of these dispatches should stop.