Hi @tristajaye, this was entirely an error on our part and has been resolved. So sorry about that- please reach out any time.