{"version":"2.1.224","anchor":"rate-limit-status-is-pushed-to-the-remote-client","canonical_anchor":"rate-limit-status-is-pushed-to-the-remote-client","heading":"Rate limit status is pushed to the remote client","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/rate-limit-status-is-pushed-to-the-remote-client","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Rate limit status is pushed to the remote client\n\nYour rate limit status now reaches a connected remote client right away.\n\n**What**\n\nRate-limit state now reaches a connected remote client immediately. On bridge connect the current state is written to the peer, and later rate-limit events are written to the bridge channel as well as the local stream. Forwarding failures are logged, not thrown.\n\n**Details**\n\n- The connect-time send is skipped if a rejection window has already elapsed, and is recorded as `bridge_rate_limit_forward`.\n- Both paths build the event through one shared helper.\n- The connect-time send is also guarded by an internal predicate whose source of truth sits outside this code path.\n\n**Evidence**\n\n`bridge_rate_limit_forward`, `rate_limit_event forward failed`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}