Hi,
It looks like that is a yet unknown bug. I was able to confirm this on our test servers as well. At the moment the only resolution would be to directly edit the plugin code. This should not be a too difficult fix, and we are preparing the new plugin release at the start of next week. If that is okay with you, I wil try including a fix to this issue within that patch as well.