Policy Service sometimes doesn’t enable automerge

[Trenly]

Sometimes Auto-Merge isn’t being enabled and it isn’t clear why. The triggers are working for most PRs, but a few are getting into a state which require a manual merge. I expect this is an issue with the policy service itself either running into rate limits or internal errors

[Trenly]

This is still in ongoing discussion with the GitOps team

[Trenly]

Pull #149544

The package for Dropbox version 197.4.7571 seems also affected by this - the commit is apparently merged but not published.

This has nothing to do with the policy service not enabling automerge

[R-Adrian]

This has nothing to do with the policy service not enabling automerge

it's been 19+ hours already since the merge happened - shouldn't it have been picked up by winget cli already?

[Trenly]

This has nothing to do with the policy service not enabling automerge

it's been 19+ hours already since the merge happened - shouldn't it have been picked up by winget cli already?

The publishing pipeline was paused for a deployment. The publish pipeline is completely separate from the policy service.

You can see in the PR you linked that the Policy Service did enable the automerge