@sueloverso, we document that any error return from WT_CONNECTION.async_new_op means we should continue to loop, looking for handles, and that seems wrong to me (and, it looks to me like there can be errors from that method that indicate we shouldn't continue. Why not call out a particular error (I'd recommend EBUSY), that implies looping, and other errors are handled as real errors?