Reported in dotnet/coreclr#27268 (comment) Maestro wasn't opening an expected dependency update PR.

I couldn't find anything intersting in the logs, and retriggering the subscription was saying the latest build had already been applied, so I manually modified the last applied build in order to get a fresh set of logs and diagnose.

Clearing up the field and retriggering the subscription opened dotnet/coreclr#27773. We should understand why the subscription had that as the latest applied build without having opened a PR in the first place, and whyy clearning it helped to get Maestro back to normal.

SubscriptionId is 86e153bd-ef9f-4f2e-df89-08d762ec7fb4