{"version":"2.1.288","anchor":"rewind-conversation-waits-for-stop-settling-and-checks-rows","canonical_anchor":"rewind-conversation-waits-for-stop-settling-and-checks-rows","heading":"Rewinding a conversation now waits for a stop to finish and refuses if history is off disk","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/rewind-conversation-waits-for-stop-settling-and-checks-rows","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Rewinding a conversation now waits for a stop to finish and refuses if history is off disk\n\n`rewind_conversation` now waits for a stopping turn to settle and refuses when the messages it would cut are no longer on disk\n\n**Unclear.** What the Send-now interruption mark changes for a user is not known.\n\n**What**\n\nThe `rewind_conversation` request, which takes a conversation back to an earlier message, now waits for any turn that is being stopped to finish settling before it cuts anything. It also refuses, with the reason `state_changed`, when the saved records of the conversation it needs are no longer on disk.\n\nThe saved conversation history now keeps track of rewrites that are still pending and of records that have been deleted. Separately, when a Send-now action interrupts a turn, the message where the conversation is cut is marked as having been interrupted that way.\n\n**Why**\n\nThese checks make rewinding in remote sessions safer against two things happening at once, such as a rewind arriving while a stop is still in progress.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}