ECS: Unable to delete empty CAS-enabled bucket - Error 1013 (HTTP: 400): Bad request body. Bucket {} is not empty

• Unable to delete an empty CAS-enabled bucket
• Error 1013 (HTTP: 400): Bad request body. Bucket {} is not empty.
• ECS CAS: No mechanism to sweep or purge reflection Clips.
• ECS CAS: Reflection Clips preventing CAS bucket from being deleted.

• A CAS object consists of one clip, and one or more blobs. 
• The clip contains the object metadata, while the blobs contain the object itself.
• When a CAS object is deleted, both the clip and the blob are deleted, and a reflection is created instead.
• The reflection contains metadata about the object which was deleted, and is treated as an object in the bucket even if they are not listed.
• Starting from ECS 3.2, a new feature called "Reflection Expiration" was introduced to CAS buckets.
• Reflection Expiration enables the ECS to expire (remove/delete) the reflections in the bucket after a certain time of their creation. 
• If Reflection Expiration is not enabled on the bucket, then the reflections created will remain in the bucket indefinitely. This makes it impossible to delete the bucket as it is not technically empty. 

Reflection Expiration must be enabled on the CAS bucket, in order for the bucket to be properly emptied and then successfully deleted.

1. Open the ECS UI.
2. Go To "Manage" on the left pane.
3. Select "Buckets".
4. Choose the namespace where the bucket is configured.
5. In the table, under "Actions", click "Edit Bucket" on the bucket which cannot be deleted.
6. Click the "Required" option at the top
7. Enable "Reflection Expiration" by pressing "On" and then choosing a value for "Reflection Age".
   The Reflection Age is the time that the reflection stays in the bucket upon creation (when the object is deleted) before it gets removed.
   The minimum value for "Reflection Age" is 1 day.
8. Click "Save" to preserve the changes.
9. Wait until the time configured in "Reflection Age" has passed before trying to delete the bucket again.
10. If the issue persists, open a Service Request with ECS support. 

Before: 
 
After: