Recent refactors removed the use of this method in favor of scheduling a single iteration on the service executor. This has made it difficult to experiment with the "thread per active operation" idea, since we never release a thread once we start the "iteration" on it. Reintroducing the use of runOnDataAvailable will not break existing code (since the ServiceExecutorSynchronous simply calls schedule directly), but gives us an opportunity to explore other executors which do cede threads back for other work between iterations.