{"version":"2.1.275","anchor":"db-read-db-write-tool-errors-now-carry-richer-diagnostic-d","canonical_anchor":"db-read-db-write-tool-errors-now-carry-richer-diagnostic-d","heading":"db_read \/ db_write tool errors now carry richer diagnostic detail","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/db-read-db-write-tool-errors-now-carry-richer-diagnostic-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### db_read \/ db_write tool errors now carry richer diagnostic detail\n\ndb_read and db_write tool errors now include extra diagnostic detail like error code, reason, and slug\n\n**What**\n\nWhen the artifacts `db_read` or `db_write` tool encounters an error, the error message shown now includes additional detail such as the error code, reason, and slug, rather than just passing along the server's raw error text.\n\n**Why**\n\nThe extra context makes it easier to understand why a database read or write inside an artifact failed, instead of seeing only a generic server message.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}