A bucket can have multiple lifecycle rules, and a single object can match more than one rule simultaneously. When multiple rules target the same objects and trigger actions on the same day, OSS applies only one action per object, determined by a fixed priority order.
How priorities work
Priority only applies when multiple lifecycle rules direct OSS to act on the same objects at the same time. When rules act at different times or target different objects, each rule runs independently.
When a conflict occurs, OSS follows this priority order, regardless of minimum storage duration or minimum storage size:
Delete objects > Convert to Deep Cold Archive > Convert to Cold Archive > Convert to Archive > Convert to Infrequent Access (IA) > Convert from IA to Standard due to recent access
Deletion always takes precedence over any storage class conversion. Among conversions, colder storage classes take precedence over warmer ones.
For fees related to storage class conversions and deletions triggered by lifecycle rules, see Fees related to lifecycle rules.
Example
The following two rules apply to the same set of objects:
Rule 1: Convert objects to IA after they have not been modified for more than 365 days.
Rule 2: Delete objects after they have not been modified for more than 365 days.
Result: OSS deletes the objects after 365 days. The conversion to IA is skipped because deletion has higher priority.