Can any of the affected locations pull the evergreen / postgresql logs from a failed attempt at removing a copy tag? I'm wondering if it's possible that a change to some database triggers may have been missed that prevents these tags from being deleted.
Can any of the affected locations pull the evergreen / postgresql logs from a failed attempt at removing a copy tag? I'm wondering if it's possible that a change to some database triggers may have been missed that prevents these tags from being deleted.