{"version":"2.1.288","anchor":"artifact-database-byte-limit-error","canonical_anchor":"artifact-database-byte-limit-error","heading":"Artifact storage gives a clear error when its total size limit is reached","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/artifact-database-byte-limit-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Artifact storage gives a clear error when its total size limit is reached\n\nAn artifact's database now refuses writes with a specific error when its total stored size hits the limit, including when a document grows\n\n**What**\n\nAn artifact can keep documents in its own database. That database can now refuse a write because it has reached its storage limit. This limit is on the total size of the documents, not on how many there are. Making an existing document larger can also be refused. Before, the only limits were on the number of documents in a collection and in the database.\n\n**Why**\n\nWhen artifact storage fills up, you get an error that says size is the problem, rather than a confusing failure.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}