@inj3ct0r and @Don The issue has been resolved with the most recent plugin update. Thanks for the report and the detailed steps provided for reproducing the issue.