{"version":"2.1.247","anchor":"grace-period-usage-flag-now-clears-at-the-reset-it-named","canonical_anchor":"grace-period-usage-flag-now-clears-at-the-reset-it-named","heading":"Grace-period usage flag now clears at the reset it named","tier":"internal","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/grace-period-usage-flag-now-clears-at-the-reset-it-named","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Grace-period usage flag now clears at the reset it named\n\nThe rate-limit grace flag now clears at the reset time the server named.\n\n**What**\n\nThe internal description of the rate-limit grace signal changed: the latched flag now clears either when a response reports no grace usage or, if the response named the grace window's reset time, once that time passes on the local clock.\n\n**Details**\n\n- The text also newly states that while the flag is set, an overage status of allowed or allowed_warning means paid extra usage covers the overflow and nothing is cut off.\n\n**Evidence**\n\n`While set, overageStatus allowed \/ allowed_warning means paid extra usage covers the overflow (nothing will be cut off).`\n\n- Area: Rate Limits\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}