The issue has been fixed.
the support was provided through private messages
the result was the update of the plugin to 1.2.7
we found a bug that has been fixed.