Update

Comments

1 comment

  • Official comment
    Jeremy Walsh

    @scott - we are aware of this bug and it is scheduled to be fixed in one of the very next releases - thank you so much for your patience!

    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk