Waiting on code owner review, yet code owners already approved.

[KaiserKarel]

We have batches failing with {"message":"Waiting on code owner review from ComposableFi/core, ComposableFi/parachain, ComposableFi/parachain-leads, and/or ComposableFi/sre.","documentation_url":"https://docs.github.com/articles/about-protected-branches"}, yet the code owners already approved.

Example of a failing PR: ComposableFi/composable#1251

Previously we had batches including a bad PR that got to staging, and then the CODEOWNERS was updated, failing the entire batch. In this case it is just this singular PR.

[vladkosarev]

We have the same issue. If the merge includes multiple PRs and some of them need CODEOWNERS approval, bors seems to get confused. Building that PR on its own is the solution but this wastes a lot of time.

[nishant-shah-social]

We are also experiencing this problem which is causing a lot of inconvenience to us.
e.g. a batch of 4 PR's getting executed -> All checks are passing -> But, then BORS decides to cancel the batch even though the concerned PR in the batch has approval from all the required code owner groups
Are there any plans to address this problem?