We scan all the environments in order to remove chain related triggers. This is very time consuming operation, it's causing significant DB and memory load and can lead to event thread starvation, especially during branch expiry

Note, if you are running into this issue and the scheduled timing of 3AM for branch expiry is particularly problematic; the schedule can be altered with a system property documented here: BAM-17644: Make Branch Expiry scheduled time configurable (fixed in Bamboo 5.15.0.1)