{"version":"2.1.228","anchor":"a-resume-mid-upload-no-longer-sends-the-wrong-transcript","canonical_anchor":"a-resume-mid-upload-no-longer-sends-the-wrong-transcript","heading":"A \/resume mid-upload no longer sends the wrong transcript","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/a-resume-mid-upload-no-longer-sends-the-wrong-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### A \/resume mid-upload no longer sends the wrong transcript\n\nResuming another conversation mid-upload no longer attaches the old session's transcript.\n\n**What**\n\nIf you resume a different conversation while a transcript backfill is still running, the upload now aborts and logs instead of pinning content from the old session onto the live one. The check runs both before the main upload and before the subagent pass.\n\n**Evidence**\n\n`[persistence-sync] Refusing backfill: session id changed since the scan anchor was pinned`\n\n- Area: Sessions\n- Names: `\/resume`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}