{"version":"2.1.257","anchor":"new-db-read-failed-message-for-artifact-reads-when-org-net","canonical_anchor":"new-db-read-failed-message-for-artifact-reads-when-org-net","heading":"New 'db read failed' message for artifact reads when org network egress is off","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-db-read-failed-message-for-artifact-reads-when-org-net","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New 'db read failed' message for artifact reads when org network egress is off\n\nWith org network access off, artifact data reads now explain the session can only read artifacts it published itself.\n\nA new \"db read failed\" error message clarifies that when an organization's cloud network access is turned off, a session can only read data of artifacts it published itself, and instructs callers not to retry.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}