all of my pipelines stopped working on Friday stuck

emalogic 5 Reputation points
2025-03-05T10:14:09.8933333+00:00

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

Azure DevOps
{count} votes

1 answer

Sort by: Most helpful
  1. Marcoz Zampieri 65 Reputation points
    2025-03-05T10:48:55.23+00:00

    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:

    1. 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.
    1. 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.
    1. 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.
    1. 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.

    1. 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.
    1. 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.
    1. 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:

    1. Review your parallel job limits in the settings to ensure you're not over the allowed limit.
    2. Check Microsoft-hosted agent availability on the service status page.
    3. Look into pipeline and agent logs to spot any issues.
    4. Verify the correctness of your YAML configuration, ensuring it includes valid steps.
    5. Cancel stuck pipelines and re-trigger them.
    6. 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:

    1. 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.
    1. 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.
    1. 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.
    1. 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.

    1. 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.
    1. 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.
    1. 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:

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

    I hope these steps help!

    I hope you can solve the problem


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.