Interesting. I'll check our deploy, not sure how many of us are on 10.12.3 yet but we haven't seen these types of issues