Currently RequestScheduling assumes that flowController.asyncRequestResource(requestResourcesDescription).get() only throws InterruptedException, and ExecutionExceptions shouldn't happen.
It was noticed that FlowController implementation can be user-provided and the user might want to throw the exception to reject the reservation request, for example the user might want to reject read requests when there are no free tokens in FlowController to leave space for more important writes.