For about a month now my logs have been filling up with throttling errors from the Echo skill app...
I've tried numerous ways to resolve the issue, including posting on the forum and opening a ticket with Hubitat support, to no avail. (I think the ticket may have ended up in Phil Collins's queue.). It doesn't actually seem to be affecting anything but it fills the logs so quickly they become basically useless for debugging other issues. This weekend I finally got frustrated enough to simply move the Echo Skill app to another hub and use hub mesh to expose just those devices I need. The Echo Skill app is the only thing running on the spare hub and it is still generating tons of errors but at least I am not using the hub for anything else.
The whole arrangement has worked out well, and I am now able to effectively use the logs on my primary hub to do what they need to do. The only issue is Alexa sometimes does not recognize a device properly, I suspect because the name is so long. In other words, because mesh appends "on primary hub" (or whatever your primary hub is named) to the end of the device name, what was "bedroom thermostat" becomes "bedroom. thermostat on primary hub." For some reason the longer name yields unpredictable results from the Alexa side. Sometimes I'll be in the bedroom and say "set thermostat to 72" and Alexa kindly changes the office thermostat too 72. Then I try setting the office thermostat to 72 and she says "office doesn't support that." So I had to manually go into the Alexa iPhone app and edit the offending device names to something shorter.
Not sure if anyone else has had (and solved) the throttling problem or knows another work-around for the really long device names... ?