Michael Stuckey

Are you trying to use the "known error" feature here to find other occurances? There is no error message or pattern listed in the configuration blob of this issue, so...

> do we preserve any logs other than those for individual build steps (and Helix work items) for known issue matching❔ No. If AzDO isn't showing the log, then it's...

Looks like the timeout happened because the `osx.1200.arm64.open` queue [was very busy](https://dotnet-eng-grafana.westus2.cloudapp.azure.com/d/queues/queue-monitor?orgId=1&refresh=30s&var-QueueName=osx.1200.arm64.open&var-UntrackedQueues=%22osx%22%2C+%22perf%22%2C+%22arm%22%2C+%22arcade%22%2C+%22xaml%22%2C+%22appcompat%22&from=1737836552419&to=1738009352419) while the job was running. Right now, I do not think there are any problems with the infrastructure....

Ah, the queue was consumed with updates and patching. The patching jobs did run longer than necessary and we've communicated with our partner team about the issue. Future jobs will...

> since doing something here seems urgent Affects customers, so I believe the proecss is that SSA should triage and establish impact

I've explicitly assigned the issue @epananth just so ownership is clear.

Also having a look at this now as part of rollout duties.

What does Ops need to do with this?

Since these config files are re-deployed with each rollout, I'm deleting any that are older than today (May 1, the latest rollout). I confirmed that unmonitored queues still get this...

I think this issue is tracking a better, automated solution in the future. It also seems like a good place to note impact and manual interventions in the meantime (which...