Gatway Rate Limit Clarification: Identify

[switchupcb]

https://discord.com/developers/docs/topics/gateway#sharding
https://discord.com/developers/docs/topics/gateway#session-start-limit-object-session-start-limit-structure
Number of identify requests allowed per 5 seconds

Is this SendEvent also limited by the the Global Gateway Rate Limit per WebSocket Connection (120 RPS) ?

[aetheryx]

The 120rps ratelimit is per websocket connection, it's max_concurrency that's global

[switchupcb]

I have updated the original thread. I understand that the 120 RPS limit is per WebSocket Connection. I also understand that max_concurrency applies to all WebSocket Connections (aggregate; Identify SendEvent). I am asking, is the Identify SendEvent is bound by solely the max_concurrency limit, or is it bound by both the max_concurrency limit and the Global Rate Limit?

[aetheryx]

technically by both, but it's a weird way to think about it. keep in mind that these two limits are pretty different, they don't know about each other. the max_concurrency limit applies to identifies, and the 120 rps limit applies to all sent payloads, which identify is one of - so yes, sending 119 pings and then an identify will hit the 120 rps limit. identify isn't specifically bound by the 120rps limit, it's inherently bound because it's a payload

you shouldn't be dealing with the 120rps limit in your identify logic (or any payload-specific logic for that matter) though - the limit is applied to all sent events so your method to send events should be keeping track of it

[switchupcb]

Of course, thanks. Implemented it correctly then.

[switchupcb]

@aetheryx answered the question in #5716 (reply in thread).