From 0857503aa4eefecf1abf418efe7448fdd8e1c17e Mon Sep 17 00:00:00 2001 From: Harshal Brahmbhatt Date: Mon, 16 Dec 2024 16:04:34 +0000 Subject: [PATCH] clarify r2 lifecycle rule conflict behavior --- src/content/docs/r2/buckets/object-lifecycles.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/src/content/docs/r2/buckets/object-lifecycles.mdx b/src/content/docs/r2/buckets/object-lifecycles.mdx index 67e80dabda98f44..1ea7e34273b9cd3 100644 --- a/src/content/docs/r2/buckets/object-lifecycles.mdx +++ b/src/content/docs/r2/buckets/object-lifecycles.mdx @@ -16,6 +16,7 @@ For example, you can create an object lifecycle rule to delete objects after 90 - An object is no longer billable once it has been deleted. - Buckets have a default lifecycle rule to expire multipart uploads seven days after initiation. - When an object is transitioned from Standard storage to Infrequent Access storage, a [Class A operation](/r2/pricing/#class-a-operations) is incurred. +- When rules conflict and specify both a storage class transition and expire transition within a 24 hour period, the expire (or delete) lifecycle transition takes precedence over transitioning storage class. ## Configure lifecycle rules for your bucket