{"version":"2.1.248","anchor":"hitting-the-weekly-reset-flow-can-interrupt-the-current-turn","canonical_anchor":"hitting-the-weekly-reset-flow-can-interrupt-the-current-turn","heading":"Hitting the weekly-reset flow can interrupt the current turn","tier":"soon","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/hitting-the-weekly-reset-flow-can-interrupt-the-current-turn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Hitting the weekly-reset flow can interrupt the current turn\n\nA limit-reset offer can now interrupt your current turn, but only if the server sends one.\n\n**What**\n\nA new interrupt reason is threaded through the turn abort paths so the limit-reset offer can stop work in progress, and a new command kind entry marks `\/limit-reset` as an action. The status block driving it is fetched from the server, so whether it ever appears depends on what the server returns.\n\n**Details**\n\n- The reason joins three interrupt\/abort classification switches, and the two menu states join the queue-state switch.\n- Status fetches that return a fieldless or non-object body are warned about rather than treated as data.\n- A limits comparison now also checks that the stored reset time matches the wall reset time.\n\n**Evidence**\n\n`[juniper-tide] status fetch returned a fieldless or non-object body (in-band error)`\n\n- Area: Usage & Limits\n- Names: `\/limit-reset`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}