A local call waiting for a slot is reached by a stop, a delete or a cancel and ends without running; what a call emits after its flow was stopped is dropped as its result is; a node run by hand whose flow is stopped or deleted tells its caller but publishes no node_error; cancelling a node also ends its calls on workers

docs/code/workers.md

@@ -96,11 +96,12 @@ Source code travels with each call and compiles on the worker, so remote-only
 dependencies do not need to be installed on the engine. Calls to `emit`,
 `save_artifact` and `load_artifact` work there too.
 
-Cancelling a run stops its active node processes. Stopping or deleting a flow
-does the same for the calls it has out, and drops an answer that still comes
-back. A disconnected worker fails in-flight calls. While executing, the agent
-sends heartbeats every ten seconds; 90 seconds without contact fails the call.
-Heartbeats do not reset the node's own silence timeout.
+Cancelling a run or a single node stops its active node processes. Stopping
+or deleting a flow does the same for the calls it has out, and drops an answer
+or emission that still comes back. A disconnected worker fails in-flight
+calls. While executing, the agent sends heartbeats every ten seconds; 90
+seconds without contact fails the call. Heartbeats do not reset the node's own
+silence timeout.
 
 Every call runs in a process group of its own. The agent kills the group when
 the engine ends the call, when the connection drops and when the agent stops,