{"version":"2.1.234","anchor":"notice-acks-now-wait-for-the-record-to-persist","canonical_anchor":"notice-acks-now-wait-for-the-record-to-persist","heading":"Notice acks now wait for the record to persist","tier":"internal","area":"Cross-Session Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/notice-acks-now-wait-for-the-record-to-persist","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Notice acks now wait for the record to persist\n\nA cross-session notice is only marked delivered once its record actually saves, otherwise it retries.\n\n**What**\n\nCross-session notices no longer ack on a best-effort flush. A new confirmed flush reports whether the delivery record actually landed, and if the upload was dropped the ack is skipped and the notice retried rather than being marked delivered.\n\n**Details**\n\n- The uploader now counts batches dropped after a 4xx response and exposes that count, which is how the confirmed flush knows whether anything was lost.\n- The retry path is recorded as `delivery_record_dropped_will_retry`.\n\n**Evidence**\n\n`delivery_record_dropped_will_retry`\n\n- Area: Cross-Session Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}