From 12f1d1e81418fe95649c21e60baf27ed159339a3 Mon Sep 17 00:00:00 2001 From: Tom Brow Date: Fri, 9 Oct 2026 12:54:57 -0700 Subject: [PATCH] docs(push): retain lease renewal suppression caveat Signed-off-by: Tom Brow --- docs/push-gateway-deployment.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/push-gateway-deployment.md b/docs/push-gateway-deployment.md index b6474946b0..9a46027490 100644 --- a/docs/push-gateway-deployment.md +++ b/docs/push-gateway-deployment.md @@ -297,7 +297,9 @@ jobs with no eligible lease. Database enqueue is conditional on a live event and an eligible lease whose recorded update timestamp is no later than event receipt. These timestamps do not establish transaction commit order. When registration and message arrival overlap, either sending or suppressing the notification is -acceptable; there is no exact enrollment-order guarantee. Activation never scans +acceptable; there is no exact enrollment-order guarantee. A concurrent lease +update, including renewal of an active lease, can also suppress a notification +under this best-effort contract. Activation never scans historical messages or deliberately backfills older notifications. This isolation requires the overlap migration and updated writers. Old images