This is occurring again in your latest version of the plugin. Clearing cache does not resolve the issue.