I won't be looking at this because this plugin is deprecated and no longer supported. I'm working on the v21.1 iteration now. I'm only leaving the link up as a courtesy, as I will be removing it once the new plugin is released. So whatever state this plugin is currently in is unfortunately the final version, bugs or not. With that said, I haven't experienced the issue you're talking about, nor has anyone else reported this bug throughout the entire lifespan of this plugin. So I'm afraid your only options are to wait for the new plugin or resolve your issue on your own.