{"version":"2.1.248","anchor":"a-failed-exit-time-transcript-write-now-aborts-the-remaining","canonical_anchor":"a-failed-exit-time-transcript-write-now-aborts-the-remaining","heading":"A failed exit-time transcript write now aborts the remaining writes","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/a-failed-exit-time-transcript-write-now-aborts-the-remaining","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### A failed exit-time transcript write now aborts the remaining writes\n\nA failed final transcript write now stops rather than continuing through other storage backends.\n\n**What**\n\nIf the final line owed to the transcript at exit fails to append through the storage backend, the session store records the error and stops, rather than logging it and continuing through the other storage providers.\n\n**Details**\n\n- The logged message text is unchanged.\n\n**Evidence**\n\n`Exit line owed to the transcript was not appended through the storage backend`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}