Currently, we rely on BFs to determine whether a release is healthy. In WRITING-36767, we encountered a scenario where a misconfiguration caused a failing test to skip BF creation. We should evaluate whether to add a manual step to the release process to review the Evergreen waterfall view. This would ensure that no failing tests exist without an associated BF.