all of my pipelines stopped working on Friday stuck

Question

all of my pipelines stopped working on Friday stuck

emalogic 5

Since Friday all of my pipelines across all projects are stuck

i did not change anything, and i have two Microsoft-hosted parallel jobs .

non of the jobs start all stuck in quoue

Pool: Azure Pipelines

Image: ubuntu-20.04

Queued: Just now [manage parallel jobs]

This agent request is not running yet. Current position in queue: 1. Current parallelism: 0. Max Parallelism for parallelism type 'Microsoft-Hosted Private': 2

Job preparation parameters

ContinueOnError: False

TimeoutInMinutes: 60

CancelTimeoutInMinutes: 5

Expand:

MaxConcurrency: 0

########## System Pipeline Decorator(s) ##########

Begin evaluating template 'system-pre-steps.yml'

Evaluating: eq('true', variables['system.debugContext'])

Expanded: eq('true', Null)

Result: False

Evaluating: resources['repositories']['self']

Expanded: Object

Result: True

Evaluating: not(containsValue(job['steps']['*']['task']['id'], '6d15af64-176c-496d-b583-fd2ae21d4df4'))

Expanded: not(containsValue(Object, '6d15af64-176c-496d-b583-fd2ae21d4df4'))

Result: False

Finished evaluating template 'system-pre-steps.yml'

Template and static variable resolution complete. Final runtime YAML document:

steps: [] User's image

please help me to resolve this

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Bodapati Harish 820 Reputation points Microsoft External Staff Moderator

2025-04-14T15:31:34.3666667+00:00
Hello emalogic,

Since the pipelines stopped running and are stuck in the queue, the issue appears to be due to no available Microsoft-hosted parallel jobs. This often happens when the organization's parallel job quota is exhausted, or all jobs are currently in use.

Please try the steps below to fix the issue:

Check your parallel job allocation in Organization Settings > Pipelines > Parallel jobs. Your log shows: Current parallelism: 0

This means no Microsoft-hosted jobs are currently available. If your limit is zero or fully used by other pipelines, new jobs will remain in queue. You may need to cancel running/stuck jobs or request additional parallel jobs based on your Azure DevOps plan.

Visit https://status.dev.azure.com/ to check if Azure DevOps is experiencing any agent-related outages that could affect pipeline execution.

Go to Pipelines > Builds, cancel all stuck builds, and then re-run a single pipeline to test if the issue is resolved once a parallel job slot becomes available.

Review your pipeline YAML or templates.

Your logs include this line: Template and static variable resolution complete. steps: []

This indicates that the resolved YAML may have no executable steps, possibly due to incorrect conditions or a broken template reference. Try testing with a minimal working YAML configuration:

trigger: - main pool: vmImage: 'ubuntu-22.04' steps: - script: echo "Test run" displayName: 'Test step'

This helps rule out any problems caused by template logic or condition evaluation.

If hosted agents are unavailable or consistently delayed, consider setting up a self-hosted agent to continue pipeline execution without relying on Microsoft-hosted infrastructure.

Helpful reference:

https://stackoverflow.com/questions/67148310/azure-devops-pipelines-stopped-running

I hope this helps. Let me know if you need any further clarification, and I’ll be happy to assist you.
Bodapati Harish 820 Reputation points Microsoft External Staff Moderator

2025-04-16T05:03:31.0066667+00:00

Hello emalogic,

Following up to see if you have chance to check the previous response and help us with requested information to check and assist you further on this.
Bodapati Harish 820 Reputation points Microsoft External Staff Moderator

2025-04-17T04:01:13.43+00:00

Hello emalogic,

We haven’t heard from you on the last response and was just checking back to see could you please provide more details on your requirement so that I can assist you further.
xixao11 0 Reputation points

2025-04-19T13:35:08.3033333+00:00

It's not a tempalte issue. I'm facing the same issue. Out of nowhere, the pipelines just stopped working. Parallel Job Limits are correct - 1 for free tier. Quota is fine, 1 available, 0 used. Microsoft-Hosted agents are available, but for whatever reason they are not picking up the enqueued job. And having the state Idle. There is nothing obvious in the log. And there is nothing wrong with the yaml. When I use self-hosted agent, the pipeline works just fine, so it's an issue with the Microsoft-Hosted agent which somehow things it's processing an item while telling me its state is Idle and that numbe of items in the queue before Item I am trying to run is 0. My enqueued item is First in the queue, so how can be anything in running before it? Doesn't make sense. Manual recreation of jobs doesn't help, cancelling doesn't help. Reaching out to Azure DevOps support is the only way, but CAN ANYONE TELL ME HOW TO REACH OUT TO AZURE DEVOPS SUPPORT for people who are suing Free tier?
Bodapati Harish 820 Reputation points Microsoft External Staff Moderator

2025-04-21T05:48:12.81+00:00
Hi xixao11,

You've already verified that the Microsoft-hosted agent quota is available and the YAML is correct, it does seem like the issue could be related to the hosted agent pool itself. It's also helpful to know that switching to a self-hosted agent allows the pipeline to run, which further suggests a potential problem with the Microsoft-hosted agents.

For users on the free tier, reaching out to Azure DevOps support directly can be limited. However, you can still report issues through the Developer Community platform:

How to report the issue:

Visit: https://developercommunity.visualstudio.com/

Sign in with your Microsoft account.

Navigate to the Azure DevOps section, and either search for similar issues or create a new one under "Azure DevOps".

1 answer

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Bodapati Harish 820 Reputation points Microsoft External Staff Moderator

2025-04-16T05:03:31.0066667+00:00

Hello emalogic,

Following up to see if you have chance to check the previous response and help us with requested information to check and assist you further on this.
Bodapati Harish 820 Reputation points Microsoft External Staff Moderator

2025-04-17T04:01:13.43+00:00

Hello emalogic,

We haven’t heard from you on the last response and was just checking back to see could you please provide more details on your requirement so that I can assist you further.
xixao11 0 Reputation points

2025-04-19T13:35:08.3033333+00:00

It's not a tempalte issue. I'm facing the same issue. Out of nowhere, the pipelines just stopped working. Parallel Job Limits are correct - 1 for free tier. Quota is fine, 1 available, 0 used. Microsoft-Hosted agents are available, but for whatever reason they are not picking up the enqueued job. And having the state Idle. There is nothing obvious in the log. And there is nothing wrong with the yaml. When I use self-hosted agent, the pipeline works just fine, so it's an issue with the Microsoft-Hosted agent which somehow things it's processing an item while telling me its state is Idle and that numbe of items in the queue before Item I am trying to run is 0. My enqueued item is First in the queue, so how can be anything in running before it? Doesn't make sense. Manual recreation of jobs doesn't help, cancelling doesn't help. Reaching out to Azure DevOps support is the only way, but CAN ANYONE TELL ME HOW TO REACH OUT TO AZURE DEVOPS SUPPORT for people who are suing Free tier?
Bodapati Harish 820 Reputation points Microsoft External Staff Moderator

2025-04-21T05:48:12.81+00:00

Hi xixao11,

You've already verified that the Microsoft-hosted agent quota is available and the YAML is correct, it does seem like the issue could be related to the hosted agent pool itself. It's also helpful to know that switching to a self-hosted agent allows the pipeline to run, which further suggests a potential problem with the Microsoft-hosted agents.

For users on the free tier, reaching out to Azure DevOps support directly can be limited. However, you can still report issues through the Developer Community platform:

How to report the issue:

Visit: https://developercommunity.visualstudio.com/

Sign in with your Microsoft account.

Navigate to the Azure DevOps section, and either search for similar issues or create a new one under "Azure DevOps".

Answer 1

hi emalogic i try to help you, It seems that your Azure DevOps pipelines are stuck in the queue, and you're unable to get them running. Don't worry, I'm happy to help you troubleshoot this. Here are some thoughtful steps you can take to resolve the issue:

Check Your Parallel Job Limits

Sometimes, even though you have two Microsoft-hosted parallel jobs, the available capacity can be exhausted due to high demand.

You can check your parallel job limits in Azure DevOps Organization Settings > Pipelines > Parallel jobs.
Make sure that the quota for parallel jobs has not been exceeded and that no other pipelines are occupying the available slots.

Verify the Availability of Microsoft-Hosted Agents

Microsoft-hosted agents are shared resources, and there can be moments of high demand, leading to delays in your pipeline execution.

Check the Azure DevOps Service Status to see if there are any ongoing issues or outages affecting agent availability.
If your organization is experiencing a high volume of traffic or there’s a temporary shortage of agents, this could explain the delays.

Review Pipeline Logs and Agent Logs

Sometimes the issue might be clearer in the logs. Review the logs for any signs of errors related to queuing, such as agent unavailability or conflicts.

Check the pipeline logs for any specific error messages that could give you more insight into the issue.
If you're using self-hosted agents, review the agent logs for any registration or connectivity issues.

Inspect the YAML Configuration

Looking at your YAML configuration, I noticed that there are no tasks listed under the steps section, which might indicate an issue with the configuration itself.

Ensure that your YAML file is properly configured with tasks and steps. Even a minimal pipeline setup needs valid steps to execute.
If you’ve recently modified the pipeline, make sure there are no conditional statements that might prevent jobs from running.

Here’s a basic template for reference:

yaml
Copia
trigger:

This ensures that the pipeline is well-formed and has executable steps.

Check the Queue Configuration

It’s also worth checking if there are any other jobs blocking the queue. Sometimes, pipelines might remain stuck because earlier jobs are still running or there’s a configuration issue.

Cancel any existing jobs that might be holding up the queue, then re-trigger the pipeline to see if it clears up.

Try a Temporary Solution

If nothing seems to be helping, you can:

Manually cancel the jobs and re-trigger them to see if the queue clears.
Restart your agent service (if you're using self-hosted agents) to ensure it's properly connecting to Azure DevOps.

Reach Out to Azure DevOps Support

If after trying all of the above steps the issue still persists, it may be helpful to contact Azure DevOps support. They will be able to assist in diagnosing any backend issues or possible service interruptions affecting your pipelines.

Summary of Helpful Steps:

Review your parallel job limits in the settings to ensure you're not over the allowed limit.
Check Microsoft-hosted agent availability on the service status page.
Look into pipeline and agent logs to spot any issues.
Verify the correctness of your YAML configuration, ensuring it includes valid steps.
Cancel stuck pipelines and re-trigger them.
Contact support if you’re still experiencing issues.

I hope these steps help!It seems that your Azure DevOps pipelines are stuck in the queue, and you're unable to get them running. Don't worry, I'm happy to help you troubleshoot this. Here are some thoughtful steps you can take to resolve the issue:

Check Your Parallel Job Limits

Sometimes, even though you have two Microsoft-hosted parallel jobs, the available capacity can be exhausted due to high demand.

You can check your parallel job limits in Azure DevOps Organization Settings > Pipelines > Parallel jobs.
Make sure that the quota for parallel jobs has not been exceeded and that no other pipelines are occupying the available slots.

Verify the Availability of Microsoft-Hosted Agents

Microsoft-hosted agents are shared resources, and there can be moments of high demand, leading to delays in your pipeline execution.

Check the Azure DevOps Service Status to see if there are any ongoing issues or outages affecting agent availability.
If your organization is experiencing a high volume of traffic or there’s a temporary shortage of agents, this could explain the delays.

Review Pipeline Logs and Agent Logs

Sometimes the issue might be clearer in the logs. Review the logs for any signs of errors related to queuing, such as agent unavailability or conflicts.

Check the pipeline logs for any specific error messages that could give you more insight into the issue.
If you're using self-hosted agents, review the agent logs for any registration or connectivity issues.

Inspect the YAML Configuration

Looking at your YAML configuration, I noticed that there are no tasks listed under the steps section, which might indicate an issue with the configuration itself.

Ensure that your YAML file is properly configured with tasks and steps. Even a minimal pipeline setup needs valid steps to execute.
If you’ve recently modified the pipeline, make sure there are no conditional statements that might prevent jobs from running.

Here’s a basic template for reference:

yaml
Copia
trigger:

This ensures that the pipeline is well-formed and has executable steps.

Check the Queue Configuration

It’s also worth checking if there are any other jobs blocking the queue. Sometimes, pipelines might remain stuck because earlier jobs are still running or there’s a configuration issue.

Cancel any existing jobs that might be holding up the queue, then re-trigger the pipeline to see if it clears up.

Try a Temporary Solution

If nothing seems to be helping, you can:

Manually cancel the jobs and re-trigger them to see if the queue clears.
Restart your agent service (if you're using self-hosted agents) to ensure it's properly connecting to Azure DevOps.

Reach Out to Azure DevOps Support

If after trying all of the above steps the issue still persists, it may be helpful to contact Azure DevOps support. They will be able to assist in diagnosing any backend issues or possible service interruptions affecting your pipelines.

Summary of Helpful Steps:

Review your parallel job limits in the settings to ensure you're not over the allowed limit.
Check Microsoft-hosted agent availability on the service status page.
Look into pipeline and agent logs to spot any issues.
Verify the correctness of your YAML configuration, ensuring it includes valid steps.
Cancel stuck pipelines and re-trigger them.
Contact support if you’re still experiencing issues.

I hope these steps help!

I hope you can solve the problem

emalogic 5 Reputation points

2025-03-05T16:26:40.0933333+00:00

Hi , checked everything nothing helped , lots of different pipelines (yaml files)

all stuck.

how can i contact azure devops support ?

Share via

all of my pipelines stopped working on Friday stuck

1 answer

Your answer