Hi @chrisaldrich I believe this is a metadata issue rather than a bug, so I have transferred this issue to our support repo and asked our support team to take a look.