Batch operations limit
There is a maximum of batch operations that can be performed at once. This means that if you try to delete (for instance) a number of objects that is larger than the maximum batch operations allowed, your request will fail.
One option would be to let it fail, currently it fails with an error that's good enough to understand the problem. But the real issue is that the user might not know that some operations internally use /batch, so it can be very confusing to understand what's going on.
Another solution would be to queue any batch requests larger than the allowed limit. This one should work in tandem with the limit of the request itself. For instance, in order to delete all the objects from a class, you need to get all the objects first. The initial get will be limited to the request limit, and if there are more objects on the class it will be necessary to paginate and queue the remaining requests before you can even run the batch request to delete them. This one takes more work and more thinking, but might be what I would like to have.