I noticed while trying to stop item traffic that this got announced "Network is stopped (xx nodes)"
But still outputs get filled and items still get transported.
Even though changes to requests don't get propagated when changing values they only get applied after restarting the network.

Uuuh, i noticed that stopping takes quite a long time, at least it stops ... Maybe a "stop" should also stop the current outputs, depending on the configured buffer size it will take much more longer, otherwise disabling the belt segments is currently a faster "workaround".

The stop actually stop the creation of new request . But the ongoing request are still processed to avoid a mess in the network.