{"version":"2.1.319","anchor":"artifact-db-remembers-undeclared-database-answer-and-gives","canonical_anchor":"artifact-db-remembers-undeclared-database-answer-and-gives","heading":"Artifact database calls stop retrying after the server says no database was declared","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/artifact-db-remembers-undeclared-database-answer-and-gives","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Artifact database calls stop retrying after the server says no database was declared\n\nAfter an artifact's database is reported as undeclared, Claude Code refuses further calls to it locally for an hour\n\n**What**\n\nWhen the server answers an artifact database call with a \"not declared\" error, meaning the artifact was not published with a database, Claude Code now remembers that answer for an hour. During that hour, further database calls for it are refused without being sent, and the message says it is repeating the server's earlier answer.\n\nOther messages changed too:\n\n- The \"not declared\" message is shorter. It no longer tells the model to republish with the database capability and retry.\n\n- A \"not found\" error on a write now explains that the database refused the write.\n\n**Why**\n\nThe model stops making the same failing call again and again, and is told plainly that retrying will not help.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}