Indeed, I'm wondering why we don't set currentBatch to null when we abort it.

Wondering if we should do the same after releasing in getBatch() and executeBatch(). Obviously, it would only work if we don't need to get access to the just executed batch after that.

It's hard to know the exact lifecycle of currentBatch from the code.

Steve Ebersole any insights?