Any advice on what to do when a repo gets stuck like this?

Hi Adam, this looks to just be a sync delay in the azure permissions not yet letting us into that repo the first time we tried. I'm replying to your email from a few minutes ago with more details shortly as soon as it's fixed!

Awesome, thank you!

😬 Of course now that I said that I'm finding more weirdness with the state this particular repo got into. I'm continuing to investigate, but might be a bit longer to get to the bottom of it and get it fixed. But I will follow up ASAP!

Originally when that repo got added, the ADO App account didn't have the Basic license, it was Stakeholder. That was corrected earlier before adding the additional repos which are working fine. I'm sure that is what led to this issue, just not sure how to correct it.

Make sense, yea. Without the right permissions we only got partial info for it, and I think we'll just need to do a more aggressive refresh on our end to pick it up now. I'm very sorry for the hiccup!

No worries, thank you for the attention to it 🙂