Trying to run a runbook (powershell) using hybrid worker group but getting error.

Question

Trying to run a runbook (powershell) using hybrid worker group but getting error.

vicky mishra 0

Trying to run a runbook (powershell) using hybrid worker group but getting error message.
The error I am getting is:-
"Job was suspended as the job limit for a hybrid worker exceeded. Add more hybrid workers to the hybrid worker group to overcome this issue, see: https://aka.ms.HRW-polling-limit exceed."

I have only 1 hybrid worker group and only 1 runbook that I am trying to run still getting this error. Attaching the image of the jobs that I ran. I need to know if I am able to connect to the server and run the job or not. Script I am trying to run is

# Create a PSCredential object using plain text (NOT recommended for production)
$username = "Some User Name"
$password = ConvertTo-SecureString "Some Password" -AsPlainText -Force
$cred = New-Object System.Management.Automation.PSCredential ($username, $password)

# Define the SCCM server name
$SCCMServer = "SCCM2" 

# Define the command to run remotely
$ScriptBlock = {
    $env:COMPUTERNAME
}

# Run the command on the SCCM server
Invoke-Command -ComputerName $SCCMServer -ScriptBlock $ScriptBlock -Credential $cred

jobs executing

2 answers

Your answer

Answer 1

Jose Benjamin Solis Nolasco 5,406

@vicky mishra I hope you are doing well,

On the worker VM: Check service Microsoft Hybrid Runbook Worker (must be running).

Restart it if it’s stuck.

Check logs at:

C:\ProgramData\Microsoft\System Center\Orchestrator\RunbookService\Logs

The “polling limit exceeded” means the worker missed Azure’s heartbeat schedule. This can happen if: The VM is low on CPU/RAM.

There’s firewall/proxy delay in reaching *.azure-automation.net.

Free up the current worker
- Stop any stuck/suspended jobs in the portal.
- Restart the Hybrid Runbook Worker service.
Option 2: Add capacity
- Add another VM to the same Hybrid Worker Group.
- This spreads the job load and avoids single-worker bottlenecks.
Option 3: Shorten job duration
- Make the runbook modular so it finishes faster, freeing the worker.

😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!

vicky mishra 0 Reputation points

2025-08-12T16:57:07.7433333+00:00
Hi Jose

Thanks for your answer.

Option 1:I have restarted the service as well as added few more lines in PowerShell script to close any running job.
Write-Output "Restarting Hybrid Worker services to clear stuck jobs..." $services = @( "HybridRunbookWorker", "HealthService", "Microsoft Monitoring Agent" ) foreach ($svc in $services) { try { if (Get-Service -Name $svc -ErrorAction SilentlyContinue) { Restart-Service -Name $svc -Force -ErrorAction SilentlyContinue Write-Output "Restarted service: $svc" } } catch { Write-Warning "Could not restart $svc: $_" } } Start-Sleep -Seconds 5

Option 2: I can not add any more machine as its a test case where I should be able to run a script.

Option 3: The script I have added is just to get system name. which I cannot change.
Still I get the same error. I am trying to run in SCCM server still got same error.

Answer 2

Hello vicky mishra, Thanks for reaching out, and we appreciate your patience while we looked into this.

From the screenshot you attached, we can see that the same runbook executes successfully when it runs on Azure but gets suspended when it targets your Hybrid Worker Group. This confirms that the runbook code itself is valid, and the issue lies specifically with the Hybrid Worker’s communication with Azure Automation.

A few additional considerations beyond the guidance already shared:

Connectivity vs. Execution: Since the job is being created on the Hybrid Worker, you are indeed able to connect to the server. The suspension is not caused by connectivity failure, but by the worker missing Azure’s required polling/heartbeat interval. Once the heartbeat issue is resolved, the same runbook should execute successfully.

Single-Worker Limitation: Even with one Hybrid Worker and one job, this error can occur if the VM experiences CPU or memory pressure or temporarily loses outbound connectivity. Azure Automation expects a consistent heartbeat, and any delay can trigger job suspension.
Monitoring Worker Health: Azure Automation provides a Hybrid Runbook Worker health feature that helps you track whether your worker is meeting heartbeat requirements and if there are any resource-related problems. Documentation: Monitor Hybrid Runbook Worker health. Scaling Out: If reliability is critical, consider adding another VM to the same Hybrid Worker Group. This allows Azure Automation to distribute jobs, which reduces the chance of a single node becoming a bottleneck.

In summary, your connection to the Hybrid Worker server is functioning correctly. The suspension is due to missed heartbeat checks rather than connectivity or authentication issues. Once the worker service stability or capacity concerns are addressed, your runbook should execute as expected.

I hope this helps clarify the issue. For further details, please refer to the Microsoft documentation:

Anurag Rohikar 600 Reputation points Microsoft External Staff Moderator

2025-08-21T13:27:44.9866667+00:00

Hello vicky mishra, Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this. Thank you!

Share via

Trying to run a runbook (powershell) using hybrid worker group but getting error.

2 answers

Your answer