Hellow,
sorry 'bout that, please try to upgrade to 3.2.2, we pushed a fix that should solve the issue.