question

Nicholas Fisher avatar image
Nicholas Fisher asked

Is there some sort of rate limiting on the AVS service.

I have created an AVS application based off the AVS sample application which uses a python client to record a request, submit it to AVS, and then record the response and play it. I often get the response:

"Sorry, I'm having trouble. Please try in a little while."

It comes back with a 200 response in the request, but there is a reference to an ErrorNotifier in the content, in addition to what seems to be the MP3 file containing the audio containing the stament above.

It comes back so that I can use it for like a minute and then goes away again. At first, I created a new security profile and produced a refresh key for it and tried it again. It worked for a minute or two, and then the same problem occurred. This makes me think that it is a rate limit / authentication issue. However, all authentication responses come back with 200. In addition, when I get the "having trouble" response, I can see the question came in properly when I view the history of that device.

Any body have thoughts?

Thanks

Nicholas Fisher

alexa voice serviceresponse
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

swasey@amazon avatar image
swasey@amazon answered

Hey Nicholas, we do not have any kind of rate limiting implemented. What times have you been making these requests? It could be that you were making requests while we were having issues or perhaps deploying new code to servers or something along those lines. A timespan would really help narrow down the issue. Also, you should have received an x-amzn-requestid header in your response as well. Could you please respond with that value so I can see what's going on?

Finally, where are you located?

10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Nicholas Fisher avatar image
Nicholas Fisher answered

Hello,

Thanks for the prompt reply.

It has been happening for the past 4 hours or so, so say 11:00 AM - 3:00 PM Pacific. It is currently happening as well. 3:11PM Pacific

I am based in San Diego. I have an echo that has been working fine all day.

The last bad one had the following in the header.

'x-amzn-RequestId': '7f863c3f-5510-11e6-9b77-51fa051a9379'

Thanks

Nicholas Fisher

6 comments
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Thanks. It does look like there is some issue on our end with your device, but I'm not familiar with what it could be, so I'll have to get back to you on what the issue is.

It also looks like you're still using the v1 API. Have you considered giving our newer v2 API a try to see if that fixes your issue? You can use your same device information in the Java reference app that we release and see if you experience the same issues.

0 Likes 0 ·

Thank you. Please let me know what you find.

As far as the v1 API, I just found a python client on the web which seemed to work, so I will take a look at updating it to V2.

0 Likes 0 ·

Hello, I was just checking to see if you had found anything out on why it wasn't working.

Thanks

0 Likes 0 ·

We've identified the issue, but I can't comment on when a fix will be available. Are you attempting to use a skill at all? For example, are you saying "Alexa, open SomeApp" or "Alexa, ask SomeApp to do SomeTask"? We might have a workaround for you if you're attempting to access a skill.

0 Likes 0 ·
Show more comments