I’ve forwarded this to our engineering team, and they’ve let me know that this isn’t expected and is a result of a bug.