Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Devops: Maximum waiter thread limit 500 is reached errors on restore #10481

Closed
MattGal opened this issue Aug 17, 2022 · 2 comments
Closed
Assignees
Labels
Azure Dev Ops Failures related to Azure Devops agents or pipelines Critical FC - Infrastructure A build failure caused by apparent infrastructure failures. Ops - First Responder

Comments

@MattGal
Copy link
Member

MattGal commented Aug 17, 2022

Sev3 Tracking IcM: https://portal.microsofticm.com/imp/v3/incidents/details/328505791/home

@MattGal MattGal added Critical Ops - First Responder FC - Infrastructure A build failure caused by apparent infrastructure failures. Azure Dev Ops Failures related to Azure Devops agents or pipelines labels Aug 17, 2022
@MattGal MattGal self-assigned this Aug 17, 2022
@MattGal
Copy link
Member Author

MattGal commented Aug 17, 2022

Azure DevOps has increased the max scale limit of their machines and the problem seems to have subsided. We'll keep this issue open til end-of-week to validate this hasn't happened again by then.

@MattGal
Copy link
Member Author

MattGal commented Aug 18, 2022

With no recurrence in 24 hours I am closing this, max scale mitigation should help in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure Dev Ops Failures related to Azure Devops agents or pipelines Critical FC - Infrastructure A build failure caused by apparent infrastructure failures. Ops - First Responder
Projects
None yet
Development

No branches or pull requests

1 participant