@sroberts is this a reproducible problem on many hosts? or something you’re running into locally?