Skip to content

Commit 12f1d1e

Browse files
committed
docs(push): retain lease renewal suppression caveat
Signed-off-by: Tom Brow <[email protected]>
1 parent 9d3d710 commit 12f1d1e

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

‎docs/push-gateway-deployment.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,9 @@ jobs with no eligible lease. Database enqueue is conditional on a live event and
297297
an eligible lease whose recorded update timestamp is no later than event receipt.
298298
These timestamps do not establish transaction commit order. When registration
299299
and message arrival overlap, either sending or suppressing the notification is
300-
acceptable; there is no exact enrollment-order guarantee. Activation never scans
300+
acceptable; there is no exact enrollment-order guarantee. A concurrent lease
301+
update, including renewal of an active lease, can also suppress a notification
302+
under this best-effort contract. Activation never scans
301303
historical messages or deliberately backfills older notifications.
302304

303305
This isolation requires the overlap migration and updated writers. Old images

0 commit comments

Comments
 (0)