We recently ran into an issue where S3 bionic rules started breaking because our CRM Accolunt ID was renamed in the source database (Looker). As a result, rules that use this field are no longer working because the header in the S3 set doesn't match the new name. Additionally, if the affected s3 set is part of a Merge or Action, it doesn't seem like we can edit it without removing the dependent sets/actions.
The only solution I've found so far is to rebuild the rule from scratch which isn't ideal when the rules have multiple sets, merges, and transformations.
