Azure Automation Account - Powershell runbook stuck in Starting (intermittently)

Justin Coon 60

Azure Automation Account - We have a Powershell runbook stuck in Starting (intermittently). Sometimes it works, other times its just stuck in Starting phase and never moves. Can't stop or cancel it

Danial Phetteplace 0 Reputation points

2023-06-13T12:37:21.0233333+00:00

I have the same issue using managed identity for the runbook. Sometimes it works just fine and sometimes it gets stuck on starting. This doesn't seem to happen with the azurerunas connection.
Philip Haglund 1 Reputation point

2023-06-14T13:11:22.2533333+00:00

Same here. Using Managed Identity with PowerShell 7.2.
Using West Europe as location.
Ron Rohlfs 16 Reputation points

2023-06-14T19:32:22.6033333+00:00

Same here.

Using Managed Identity with PowerShell 7.2.

Location: West US 2
Cook, Rhonda K 0 Reputation points

2023-06-15T14:17:13.6966667+00:00

Same here, we are using a MI and Powershell 7.2 and experiencing the same issues, location is East US
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-06-20T09:02:38.0266667+00:00
@Justin Coon ,

Apologies for the delayed response. Can you please answer the queries below:

Is your runbook using ManagedIdentity for authentication as well, which gets stuck?

When is it stuck what happens next? Does it resume on its own?

Is it happening only with specific runbook (and other runbook jobs working fine)?

For the jobs which are stuck, please see if there are any exception logged under the "Exception" tab as shown below:

Are you passing specific parameters to your runbook - for example, array/string etc? A sample code snippet should help understand the runbook.

Please let us know the answer to the question above to help us better undestand the scenario.
Atond 0 Reputation points

2023-06-21T08:49:59.85+00:00
Hello,

I have the same problem with a script :

$groupe_ressource = Get-AutomationVariable -Name 'var_ressourcegroup' $hostpool = Get-AutomationVariable -Name 'var_hostpool' $groupe_ressource = $groupe_ressource.Replace("`"","") $hostpool = $hostpool.Replace("`"","") try { "Logging in to Azure..." Connect-AzAccount -Identity -AccountId "<<redacted>>" } catch { Write-Error -Message $_.Exception throw $_.Exception } Update-AzWvdHostPool -ResourceGroupName $groupe_ressource -Name $hostpool -LoadBalancerType 'BreadthFirst'

And in exception i have :

The job was stopped because it did not complete after three attempts. Please try re-submitting a new job.

Sometines, the script doesn't find automation variable :

Get-AutomationVariable: Line | 5 | $groupe_ressource = Get-AutomationVariable -Name 'var_ressourcegroup' | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | {"type":"https://tools.ietf.org/html/rfc7231#section-6.6.1","title":"An error occurred while processing your request.","status":500,"traceId":"00-60790e2695fbae5a4e013faf4e1b530b-0e0d351c106633c0-00"}
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-06-21T09:28:11.9866667+00:00

Atond, thank you for the comment and I regret the inconvenience. The error in this case is "Internal Server error 500" which is related to the host itself which is processing the resource. I would suggest opening a support case so that it can be investigated at host level for your specific Automation Account - https://azure.microsoft.com/en-in/support/create-ticket
Peter van Rossum 30 Reputation points

2023-06-26T13:10:18.8466667+00:00

Same problem here. Jobs are stuck in "Starting".
I'm also using PowerShell 7.2 and Managed Identity.
I tried to use Stop-AzAutomationJob from an other runbook to stop the job, however that throws an error:

"The requested update for the Job is not allowed. The job already has a pending action."

What is the correct way to stop a job that is stuck in "Starting"?
And what is the cause? Can we avoid it?
Harsh Damania 1 Reputation point

2024-01-09T11:22:27.4366667+00:00

having the same issue north europe all jobs are getting queued
Report PowerBI 10 Reputation points

2024-01-10T03:26:43.3233333+00:00

Having the same issue at Southeast Asia region. All scheduled jobs was failed yesterday with Powershell exception error. And queued for long time (hours) today.
AnuragSingh-MSFT 21,566 Reputation points Moderator

2024-01-10T05:46:26.6966667+00:00

Hi Everyone, Apologies for the inconvenience because of this issue. Based on the issue being reported, the Automation team is investigating this issue. Please follow the latest thread below on this thread which will have latest update -

https://learn.microsoft.com/en-us/answers/questions/1485512/runbook-jobs-getting-queued-status

7 answers

Abdullah 31 Reputation points

2024-05-03T15:37:53.6233333+00:00

Has anyone figured out why this is happening? I have code which requires PS 7.2 but the runbooks just go into SUSPENDED state. I see not logs or error on the Automation Account nor on the Hybrid Worker.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Lorenzo Righini 10 Reputation points

2024-07-30T09:49:14.9166667+00:00

We are experiencing the same issue here.

We have a few cloud-only runbooks that were updated from PowerShell runtime 5.1 to 7.2 on a custom runtime environment, it happens that from time to time some runs never actually start, they're stuck in Starting status and, after some time, they get Suspended without any error message I could see.

Did anyone find a cause?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Automation Account - Powershell runbook stuck in Starting (intermittently)

7 answers

Your answer