Websocket rate limit exceeded

@dsj @corrineb - Sorry for bringing an older thread back to life - but I’m starting to get these errors in some of my own Web services testing for my open source project. Another older thread talks about this mainly for a defensive nature. Is there a way to understand what the actual rate limit is? I’ve certainly seen this for too many socket connections but also just now see it for the entirety of an access token connection where I was pulling in historical data. I can certainly look at throttling some of these queries, but they’re not super crazy (in my opinion). Should I open a ticket to talk about these restrictions, or can it be shared in the forum?