Hello @Jennings, @alex
Thank you for reporting the issue with the CLI tool. We have opened a ticket internally, and we are currently investigating the underlying issue that is giving rise to the error. We do not have a fix in place yet, but we’re working diligently to address the problem. We hope to have a solution in place in the next release cycle.