{"version":"2.1.311","anchor":"task-file-download-refactored-with-a-new-destination-model","canonical_anchor":"task-file-download-refactored-with-a-new-destination-model","heading":"New wording when a session cannot save task files","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/task-file-download-refactored-with-a-new-destination-model","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### New wording when a session cannot save task files\n\nSaving files from tasks was reorganised, and the error for a session with nowhere to save now says it cannot save task files\n\n**What**\n\nSaving files that come from tasks now goes through a shared set of steps: a check before starting, a check that there is enough disk space, and then opening the file for writing. Destinations are now described as places, and some destinations can report that saving there is always refused.\n\nWhen a session has nowhere to save files, the message now reads \"this session cannot save task files.\" It used to read \"this session keeps no files on this computer.\"\n\n**Why**\n\nThis changes how failed task file downloads are reported and where those files can be saved.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}