Accepted Solutions (1)

Accepted Solutions (1)




Good catch - this looks to be 100% a bug on our end, if you're able to consistently reproduce it.

I would recommend creating having a Supported user create an incident with customer care - they have the proper resources to get the info to engineering so we can push a fix out for it.