for some reason S3Bucketlogs was holding, and no was no reason of knowing why. Cloudtrail seems to be a solution in terms of properly debugging the situation.
Capture and consolidate user activity and API usage across AWS Regions and accounts on a single, centrally controlled platform.
AWS Cloudtrail
https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-stuck-progress/
https://console.aws.amazon.com/cloudtrail/home?region=us-east-1#/
https://aws.amazon.com/premiumsupport/knowledge-center/s3-conflicting-conditional-operation/
After you send a request to delete a bucket, Amazon S3 queues the bucket name for deletion. A bucket name must be globally unique because the namespace is shared by all AWS accounts. Because Amazon S3 is a large distributed system, changes like deleting a bucket can take time to become eventually consistent across all AWS Regions. You can get the error “A conflicting conditional operation is currently in progress” if you try to create a new bucket with the same name during the process of deleting the original bucket.
Aws
Fixed the problem by creating a new stack with a new namespace