I have exactly the same problem. I think it is the new update of the Plugin, because that’s when the glitch started. I even uninstalled and reinstalled the plugin to see if it works. It didn’t.
I have now sent a support request to Amazon Associates and will see what the outcome is. Maybe you can do the same? I will however post their response when I get it.
