{"version":"2.1.271","anchor":"artifact-file-list-now-distinguishes-single-page-no-files","canonical_anchor":"artifact-file-list-now-distinguishes-single-page-no-files","heading":"Artifact file-list now distinguishes 'single page, no files' from a real 404","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/artifact-file-list-now-distinguishes-single-page-no-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Artifact file-list now distinguishes 'single page, no files' from a real 404\n\nArtifact file listing now clearly reports 'single page, no files' instead of a generic not-found error\n\n**What**\n\nWhen you list the files for an artifact that turns out to be a single page with no separately published files, the tool now returns a specific `single_page` error reason with a clearer explanation. Previously this case was lumped in with genuine not-found (404) errors and handled the same way.\n\n**Why**\n\nThis makes it clear when an artifact simply has no separate files to list, rather than making it look like a broken or missing artifact.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}