Always Throttling

I’m getting the same error with the following ajax referrer.

https://mysite/wp-admin/admin-ajax.php?action=aalb_update_table

I’m not logged in at the moment so it’s not like I’m looking up loads of products.

The guidelines suggest that you have to make sales to be allowed to use the API.

https://docs.aws.amazon.com/AWSECommerceService/latest/DG/TroubleshootingApplications.html#efficiency-guidelinestarget=_blank

I’ve blanked out my API settings for the time being and will manually create my shortlinks.

The weird thing is that I’ve had sales until this happened. I think they’ve got a bug because I tried my API info in their Sandbox and it fails there too. I might need to contact Amazon.

Found this explanation which basically tells me they’ve messed up their throttling because this number is FAR above my usage.

Effective 23-Jan-2019, the request limit for each account is calculated based on revenue performance attributed to calls to the Product Advertising API (PA API) during the last 30 days.

Each account used for Product Advertising API is allowed an initial usage limit of 8640 requests per day (TPD) subject to a maximum of 1 request per second (TPS). Your account will receive an additional 1 TPD for every 5 cents or 1 TPS (up to a maximum of 10) for every $4320 of shipped item revenue generated via the use of Product Advertising API for shipments in the last 30 days.

Note that your account will lose access to Product Advertising API if it has not generated referring sales using PA API in the last 30 days.

I’ve got just 24 links on my whole so I can’t see why it would be constantly trying to check them.

I had a dig into the code. And found a file called “cron_constants.php”. In there there was a reference to the update that was recorded in the error logs. It mentioned it was 15 minutes. So I’ve incremented that to 12 hours.

const UPDATE_TABLE_CRON_SCHEDULE_DEFAULT_VALUE = 43200?;

Hopefully, this will quiet things down a bit. Annoyingly, the plugin does not render the links if you bank the API keys (which are just used for creating and checking the codes) so you can’t just remove those to stop it calling the API.

I’ve also noticed that my wp-options table has become bogged down with 133,000+ rows from this plugin. Option value indicates it’s some kind of cache record. I culled the oldest 132,000 records and my site responds faster and the plugin seems to be a little better behaved. I also implemented the const UPDATE_TABLE_CRON_SCHEDULE_DEFAULT_VALUE = 43200?;