Solution approaches<\/h4>\n
First recommendation:<\/strong> Use the server-side cron job.<\/p>\n You can use the ASA2 cronjob to avoid this. It can also be used without server-side configuration using the WP Cron API. For more details check out the cronjob manual<\/a>.<\/p>\n Second recommendation:<\/strong> If the server-side cronjob cannot be used, use the option „Client-side request limit handling<\/strong>“ available since version 1.14 which can be found in ASA2’s options section „Advanced“.<\/p>\n Since ASA2 version 1.14 it is possible to display the frequency of API requests<\/strong> in the form of a diagram and to identify the reason for the requests with a detailed list (see screenshot below). This can be activated with option „Logging \/ Record API stats<\/strong>„.<\/p>\n Just as likely is that the frequency of your requests is wrongly calculated<\/strong> by the Amazon PA API. For many users who receive this message, it also occurs via the Amazon PA API Scratchpad<\/a><\/strong>, which is a test environment of Amazon itself.<\/p>\n I know from other plugin developers that they are confronted with the same problem<\/strong>. This is not an issue of ASA2 alone. This is also evident from this discussion in the Amazon forum<\/a>, where people report the same problem without using ASA.<\/strong><\/p>\n Here is a demo video showing that the error occurred on Amazon’s Scratchpad even though no request was sent for at least a few seconds:<\/p>\n![\"\"](\"https:\/\/www.wp-amazon-plugin.com\/wp-content\/uploads\/2020\/10\/asa2_pa_api_request_stats_logo-300x178.jpg\"){kind=logo}
<\/a><\/p>\nReason 2<\/h2>\n