As of now, the master only sends TaskUpdated messages to subscribers when the latest known task state on the agent changed:
The latest state is set like this:
However, the `TaskStatus` message included in an `TaskUpdated` event is the event at the bottom of the queue when the update was sent.
So we can easily get in a situation where e.g. the first TaskUpdated has .status.state == TASK_STARTING and .state == TASK_RUNNING, and the second update with .status.state == TASK_RUNNNING and .state == TASK_RUNNING would not get delivered because the latest known state did not change.
This implies that schedulers can not reliably wait for the status information corresponding to specific task state, since there is no guarantee that subscribers get notified during the time when this status update will be included in the status field.