Reply to 1202744518438604801

@afanad @useloom They wrote yesterday:

"Our Engineers tackled this bug and released a new version of the extension 3.3.60.

Please make sure you're on the latest version and verify that the issue is no longer happening."