Support » Plugin: Amazon Associates Link Builder » You are submitting requests too quickly.

  • Resolved Laz

    (@lazharichir)


    Hello,

    Just checked my PHP error log and over the last weeks, I have dozens of “You are submitting requests too quickly” errors per hour. I understand there is throttling going on with AWS’ Product Advertising API but…

    Isn’t caching in the plugin here for that precise reason? Is the caching broken so that so many requests are made so often? Is there any way to increase the quota allowed by purchasing credits for example?

    Lastly, when this error is displayed in my PHP log, does it mean the visitor doesn’t see the actual page and sees the error too? Or is this just an error saved in the logs?

Viewing 3 replies - 1 through 3 (of 3 total)
  • I was getting this as well even though it was the first search. It seemed to clear up on its own for me and not seen it in the past few days.

    Plugin Author Amazon Associates Link Builder

    (@amazonlinkbuilder)

    Dear users,

    The error: “You are submitting requests too quickly” is due to throttling and details about the allowed request count per second is mentioned here. If there are multiple shortcodes on a page, you might be shown this error depending upon your allowed Transaction count per second(TPS) i.e. if your TPS is 4, only 4 shortcodes will be rendered in a second for the first request made and then cached for 30 minutes which will allow another 4 new shortcodes to render in next request hit.
    we are currently maintaining a caching of 30 minutes so the first user in every 30 minutes might face this issue and in that case, the requests that are above the allocated quota per second will get throttled and the first user will not see products from those shortcodes.

    We are working to fix this soon so that users can see products even in case you are throttled due to low TPS.

    My php log is full of this message too. However, I am only using one shortcode (containing a maximum of 10 ASINs) per page view at most. Also there are only about 17 different shortcodes (containing different combinations of about 30 ASINs) on the whole website. I would expect that the plugin manages to provide this little amount of content without violating your own “Efficiency Guidelines”.

    How about caching each ASIN info for 30 minutes and implementing a server-to-server update logic according to the allowed TPS and displaying cached content if updating takes too long?

    Can I expect this problem to be solved for my use case as mentioned above or do I have to find a different solution?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘You are submitting requests too quickly.’ is closed to new replies.