Pool provider seems slow, we notified pool provider at 26/08/2026 20:06:18, still agent has not started processing it. Pool provider delay(in mins): 17.378977555

Question

Pool provider seems slow, we notified pool provider at 26/08/2026 20:06:18, still agent has not started processing it. Pool provider delay(in mins): 17.378977555

Fini Hanfiro 0

This is using the Azure Pipelines: ubuntu-latest agent . I can't see any outage notices in Azure DevOps status page

Fini Hanfiro 0 Reputation points

2026-08-26T21:47:19.0433333+00:00

The pipeline timed out and on a manual trigger of the pipeline, the agent was able to pick up the job. Not sure what happened but will mark this as resolved for now.
Gursimran Singh 570 Reputation points Microsoft External Staff Moderator

2026-08-26T23:05:21.8433333+00:00
Hi @Fini Hanfiro ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

If this issue recurs, the same troubleshooting steps outlined below can be followed to diagnose

Possible Causes & Troubleshooting Steps:

Agent Status – Check whether the Agent is in an 'Online/Ready' state. If the Agent is 'Not Ready', 'Paused', or 'Offline', tasks remain pending in the queue. Also verify the Agent's last heartbeat timestamp.

Network Connectivity – There could be network latency or packet loss between the Agent and Pool Provider, causing delays in delivering the task assignment message. Check ping/traceroute results and connection logs, and verify firewall/proxy timeout settings.

Queue Load – If the Pool Provider is receiving a high volume of tasks and there aren't enough available agents, processing delays are expected. Review queue length and current load via the dashboard.

Agent Service Restart – If the Agent process has hung (stuck thread, memory leak, crashed listener), a clean restart of the Agent application/service may resolve the issue. Save or complete any in-progress work safely before restarting.

Log Review – Review logs from both Agent and Pool Provider around the timestamp 20:06:18 to identify any errors, timeouts, or exceptions (such as 'connection refused', 'authentication failure', 'task rejected').

Polling Interval – Check the Agent's polling interval configuration (how frequently it requests new tasks from the Pool Provider). If this interval is set too long, adjusting it may reduce the delay. Also check API rate-limit settings during this review

Your answer

Fini Hanfiro 0 Reputation points

2026-08-26T21:47:19.0433333+00:00

The pipeline timed out and on a manual trigger of the pipeline, the agent was able to pick up the job. Not sure what happened but will mark this as resolved for now.
Gursimran Singh 570 Reputation points Microsoft External Staff Moderator

2026-08-26T23:05:21.8433333+00:00

Hi @Fini Hanfiro ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

If this issue recurs, the same troubleshooting steps outlined below can be followed to diagnose

Possible Causes & Troubleshooting Steps:

Agent Status – Check whether the Agent is in an 'Online/Ready' state. If the Agent is 'Not Ready', 'Paused', or 'Offline', tasks remain pending in the queue. Also verify the Agent's last heartbeat timestamp.

Network Connectivity – There could be network latency or packet loss between the Agent and Pool Provider, causing delays in delivering the task assignment message. Check ping/traceroute results and connection logs, and verify firewall/proxy timeout settings.

Queue Load – If the Pool Provider is receiving a high volume of tasks and there aren't enough available agents, processing delays are expected. Review queue length and current load via the dashboard.

Agent Service Restart – If the Agent process has hung (stuck thread, memory leak, crashed listener), a clean restart of the Agent application/service may resolve the issue. Save or complete any in-progress work safely before restarting.

Log Review – Review logs from both Agent and Pool Provider around the timestamp 20:06:18 to identify any errors, timeouts, or exceptions (such as 'connection refused', 'authentication failure', 'task rejected').

Polling Interval – Check the Agent's polling interval configuration (how frequently it requests new tasks from the Pool Provider). If this interval is set too long, adjusting it may reduce the delay. Also check API rate-limit settings during this review