Hey @Philix
Thanks for catching this. We’ve sent it to the team to see if we can observe the same issue.