Comments

1 comment

  • Official comment
    Kim S.

    Hi Robin,

    Thank you for reaching out and bringing this to our attention!

    Our engineering team has found the root cause of this issue and implemented a fix. This fix will be available in our next update, version 3.59, which we anticipate releasing before the end of this week. 

    I have turned this post into a ticket and will update you as soon as the release is available. 

    Thanks again, 
    Kim 
    Sr. Customer Support Manager

    Comment actions Permalink

Post is closed for comments.