{"version":"2.1.299","anchor":"project-doc-write-refusals-with-if-version-guidance","canonical_anchor":"project-doc-write-refusals-with-if-version-guidance","heading":"Clearer messages when a project document write is refused for a version mismatch","tier":"notice","area":"Projects","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/project-doc-write-refusals-with-if-version-guidance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Clearer messages when a project document write is refused for a version mismatch\n\nRefused project document writes now say the document changed since the given version and how to retry, or that the version cannot be checked\n\n**Unclear.** Which tool or feature writes these project documents is not stated.\n\n**What**\n\nA write to a project document can name the version it expects to replace, using `if_version`. The messages shown when such a write is refused have been reworded. Each one says that nothing in the project was changed, and covers one of two cases:\n\n- The document changed since the version given in `if_version`. The message explains how to retry, up to two times.\n\n- The session cannot check `if_version` at all.\n\n**Why**\n\nThis protects a project document from being overwritten with stale content, and the new wording says what to do next.\n\n- Area: Projects\n- Names: `if_version`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}