Yep, we've been testing 17.2 and it is churning up all the needle in a haystack issues. Luckily this particular one is the last to be cleared from the 17.2 heap and put into the our implementation is broken heap 🙂