{"version":"2.1.267","anchor":"artifact-publish-responses-can-now-report-deadlinedropped","canonical_anchor":"artifact-publish-requests-can-now-be-dropped-for-exceeding-a","heading":"Artifact publish responses can now report a dropped deadline","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/artifact-publish-responses-can-now-report-deadlinedropped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Artifact publish responses can now report a dropped deadline\n\nArtifact publish\/deploy responses now report deadlineDropped when a request's deadline was exceeded\n\n**Unclear.** The finding does not say what causes a deadline to be dropped during publish, or what a caller is expected to do in response.\n\n**What**\n\n- The artifact-publish response now includes a `deadlineDropped: true` field when a request's deadline was exceeded.\n\n- The deploy\/publish response path now passes a `sent` flag into error classification, and downstream field-inclusion logic takes into account whether a deadline was set.\n\n**Why** This surfaces to callers when an artifact publish request was dropped for exceeding its deadline, rather than failing silently or ambiguously.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}