{"version":"2.1.247","anchor":"background-task-output-survives-write-failures-and-says-so-w","canonical_anchor":"background-task-output-survives-write-failures-and-says-so-w","heading":"Background task output survives write failures, and says so when it does not","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/background-task-output-survives-write-failures-and-says-so-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Background task output survives write failures, and says so when it does not\n\nBackground output writing now retries, logs once per error type, and tells you exactly what was dropped.\n\n**What**\n\nThe writer that saves a background task's output now tracks whether it is failing, how many characters are still unwritten, and whether anything was lost. Repeated retry errors are logged once per class rather than every attempt, and past a threshold the queued output is dropped with an error naming exactly how many characters were discarded.\n\n**Details**\n\n- Retry errors are grouped as disk exhaustion or unexpected, so a full disk does not flood the log.\n- A write that throws re-queues its marker instead of losing its place.\n- When output is truncated for hitting the on-disk cap, the notice now replaces the chunk it truncates instead of being appended next to it.\n\n**Evidence**\n\n`Task output still cannot be written`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}