“This was simply an error tied to a specific regional build, and it’s now been corrected.”