{"version":"2.1.277","anchor":"rate-limit-usage-schema-adds-severity-and-is-active-fields","canonical_anchor":"rate-limit-usage-schema-adds-severity-and-is-active-fields","heading":"Rate-limit and usage-meter entries now always include severity and is_active","tier":"internal","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/rate-limit-usage-schema-adds-severity-and-is-active-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Rate-limit and usage-meter entries now always include severity and is_active\n\nUsage and rate-limit data from the server now always states each entry's severity and whether it is currently active\n\n**Unclear.** How severity and is_active are used or surfaced to the user isn't stated in the finding.\n\n**What**\n\n- The rate-limits API response schema gained two new fields on each limit entry: `severity` and `is_active`, alongside the existing group, percent, resets_at, and scope fields.\n\n- A related status-meter schema, used for usage\/limit meters more broadly, changed `severity` and `is_active` from optional and nullable fields to required ones, with an updated description clarifying that every row's severity and active status comes from the server, not something a client computes itself.\n\n**Why**\n\nThis ensures any client displaying usage or rate-limit information always gets a definitive severity level and active\/inactive status straight from the server, instead of having to infer it or handle missing values.\n\n- Area: Rate Limits\n- Names: `severity`, `is_active`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}