I'm finding it very difficult to hard test my Proactive Events API skill because the documents do not specify at all what the limits are for sending out notifications on a per-user basis. Now I'm stuck again with a skill in development that I can't do anymore work with because I am getting TOO_MANY_REQUESTS errors when I send out a notification.
Last time I got that error it poisoned my skill's Client ID & Secret pair so that I could never use them again. I had to create a completely new skill just to get a new Client ID & Secret pair just to get working again. When I got that error last time, I instituted checks in my code to wait at least two minutes between sending notifications because sending out more than that immediately triggered the error.
This time, after sending out about 40 notifications, I got that error again. Worse, I cleared all the pending notifications from my device and an hour later it's still dead. I have lost a ton of time trying to guess what the limits of the Proactive Events API and I can't imagine for the life of me why those limits aren't documented somewhere plainly. It's been at least a year since the API's release. There is only the mention of a single 25 transactions per second limit for the entire skill. That's it.
Remember, I am doing this with an Alexa skill that is unpublished(development mode) on my personal Alexa device. Shouldn't I be able, as a professional developer, to send out as many notifications as I like since that is what any good developer does during hard testing?
The current workflow with the Proactive Events API is very painful because of this, which is a shame because it's a well designed API and a killer feature.
- Tell me if my skill is now permanently banned from sending notifications like last time or if not, how long do I have to wait now?
- Document all the Proactive Event API limits that lead to the dreaded TOO_MANY_REQUESTS error. Number per customer per minute, per hour, per day, all of it please!
- Give us a known fast contact route where we can get our skills "reset" when this error happens. It's a skill-killer.