{"version":"2.1.239","anchor":"reading-published-files-from-a-cloud-session-now-reports-why","canonical_anchor":"reading-published-files-from-a-cloud-session-now-reports-why","heading":"Reading published files from a cloud session now reports why a read was refused","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/reading-published-files-from-a-cloud-session-now-reports-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Reading published files from a cloud session now reports why a read was refused\n\nFailed reads of published cloud files now say whether the credential, the artifact, or a missing relay was the problem.\n\n**What**\n\nListing and reading files from a published artifact go through the session gateway relay only, and failures now say which kind they are: a credential the gateway would not accept, an artifact the relay refused, or a session with no relay at all, which cannot retry the read locally.\n\n**Details**\n\n- The relay-only path also turns off the public-read fallback.\n- A 403 or 404 from the relay is reported as a refusal; a 401 is the new unauthorized case, which did not exist in v2.1.238.\n\n**Evidence**\n\n`the session gateway did not accept this session's credential for the artifact relay; retrying from here will not help`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}