Azure DevOps – This agent request is not running because you have reached the maximum number of requests

Objective: In this blog post, we will learn a why the error This agent request is not running because you have reached the maximum number of requests that can run for parallelism type ‘Microsoft-Hosted Private’ occurs and also see if there are any workarounds.

Advertisements

Background:

Azure DevOps (in short ADO) is an Application Life Cycle Management (ALM) tool that helps you to manage your application end-to-end.

ADO helps us in automating the Build and Release process. In order to automate, you would need to create pipelines.

Advertisements

Microsoft Build Agents:

If you would like to build your pipelines (for automating any of your tasks) using Azure DevOps, then you need Compute power in order to execute / run the pipeline. By default, Microsoft (used to) provides Microsoft hosted Virtual Machines called Azure Pipelines. When you use the Azure Pipeline Hosted Agent, a fresh Azure Virtual Machine is allocated for executing the pipeline.

If you have started working on exploring Azure DevOps pipelines recently, then you would have faced an issue with the message This agent request is not running because you have reached the maximum number of requests that can run for parallelism type ‘Microsoft-Hosted Private’. Current position in queue: 1 as shown in the below screenshot

Azure DevOps - This agent request is not running because you have reached the maximum number of requests
Azure DevOps – This agent request is not running because you have reached the maximum number of requests

This error occurs because of the recent changes that Microsoft has introduced as the Free Agents are being abused.

Advertisements

The error occurs when you try to run a pipeline in any Project in a new Organization. Microsoft documentation says that this change is applicable for only public projects, but I have noticed that same even in new Private Projects created in new Organization.

Advertisements

For more information about official announcement, you have read at https://devblogs.microsoft.com/devops/change-in-azure-pipelines-grant-for-public-projects/

In order to solve this problem for any projects created in a new Azure DevOps Organization, you need to have your own Private / Self-Hosted Agent. You can read more about how to set up a Private agent, you can read the below article.

Azure DevOps – Configure Self Hosted Agent for Azure Pipelines

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s