You can modify the storage class in either of the following ways:
This may be caused because the object contains special characters. You can set a lifecycle rule to delete it.
You can set a lifecycle rule to specify the number of days to transition objects to ARCHIVE or delete them after they are uploaded. For detailed directions, please see Setting Lifecycle. You can also use an SDK to set a lifecycle (see Android SDK - Lifecycle or Java SDK - Lifecycle).
You can set a lifecycle rule to automatically transition objects to another storage class or delete them.
You can set a lifecycle rule and enable Managing historical versions to transition objects or delete historical object versions.
You can configure up to 1,000 lifecycle rules for a bucket. For more information, please see Lifecycle Overview.
It is recommended that you do not configure conflicting lifecycle rules for the same set of objects in COS, because this may result in different fees.
Rules configured at any time will always start executing at 00:00 the next day (GMT+08:00). As objects are executed asynchronously, the execution of qualified objects uploaded after the rule is configured will be completed before 24:00 the next day in most cases.
For example, you configured a lifecycle rule at 15:00 on the 1st day of the month to delete files one day or longer after they are modified. Then, at 00:00 on the 2nd day, the lifecycle task scans for files that were modified over one day ago and deletes them. Files uploaded on the 1st day will not be deleted at 00:00 on the 2nd day, as the time elapsed since their modification is less than one day. Instead, these files will be deleted at 00:00 on the 3rd day.
In lifecycle configuration, Deleting incomplete multipart means to delete incomplete multiparts generated by multipart upload. Parts that are uploaded but not merged become incomplete multiparts, which take up storage but cannot be downloaded. You can check Deleting incomplete multipart as needed.