@ttscoff Latest update (17.1.1) calls out specifically that it addresses this. Weird oversight for sure.