{"version":"2.1.236","anchor":"clearer-artifact-tool-errors-for-bad-links-and-oversized-pag","canonical_anchor":"clearer-artifact-tool-errors-for-bad-links-and-oversized-pag","heading":"Clearer Artifact tool errors for bad links and oversized pages","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/clearer-artifact-tool-errors-for-bad-links-and-oversized-pag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Clearer Artifact tool errors for bad links and oversized pages\n\nArtifact tool errors now tell you what to do next instead of just what broke.\n\n**What**\n\nThe Artifact tool's failure messages now tell you what to do next instead of describing what went wrong. A URL that is not an Artifact link now names the expected `...\/code\/artifact\/<uuid>` form and says to pass an existing Artifact link or omit `url` to create a new one, and a page that exceeds the size cap now comes back as advice on how to slim it down rather than a bare thrown error.\n\n**Details**\n\n- The unrecognised-link message points at the tool's `list` action for finding existing Artifacts, with the text `(action: \"list\" shows them).`\n- The old wording suggesting a publish may have succeeded despite the error is no longer used here; it has moved to a different failure case.\n- The size-cap message reads `Shrink the page \\u2014 move large inline assets (base64 images, embedded datasets) out of it or split the content across several artifacts \\u2014 then retry.`, naming base64 images and embedded datasets as the usual culprits and splitting across several Artifacts as the alternative.\n\n**Evidence**\n\n`(action: \"list\" shows them).`, `Shrink the page \\u2014 move large inline assets (base64 images, embedded datasets) out of it or split the content across several artifacts \\u2014 then retry.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}