RunCommand stuck in cancelling state

Question

RunCommand stuck in cancelling state

Kaushik Srinivas 20

On our AVS SDDC a couple of run commands are stuck in cancelling state. As a result of this we are not able to submit any new run command.

Could you please let us know how to resolve this.

Screenshot 2026-05-05 at 10.59.17 AM

Anonymous

2026-05-05T09:42:49.58+00:00
Hi Kaushik,

Thank you for providing the details. The behavior you're experiencing with Run Command is expected in Azure VMware Solution. Run Commands are executed one at a time in the order they're submitted. If a command stays in a “Cancelling” or “Pending” state, it can prevent new commands from running.

To address this, you can try these supported steps:

Retry cancellation in the portal

Open your AVS private cloud in the Azure portal

Go to Operations -> Run command -> Run execution status

Select the affected execution

Click Cancel + delete and confirm

Retry using the Packages view

Navigate to Operations -> Run command -> Packages

Select the relevant package (e.g., Microsoft.AVS.Management)

Go to Run execution status

Find the execution and use More (…) -> Cancel + delete

These steps will try to cancel the execution and remove it after the backend operation is finished.

Allow time for backend processing

After cancelling, wait a bit and refresh the portal

The status might remain “Cancelling” for a while as cleanup completes

If the execution remains stuck

There isn’t a supported way to forcefully remove a run command execution besides the portal actions above

If the state doesn’t change or continues to block new commands, backend assistance is usually needed

Let me know how it turns out for you.

References:

https://learn.microsoft.com/en-us/azure/azure-vmware/using-run-command
Kaushik Srinivas 20 Reputation points

2026-05-11T08:06:25.6366667+00:00

Tried the steps in the earlier comment and i still can see, one run command in cancelling state.
Anonymous

2026-05-12T06:25:08.51+00:00

Hello Kaushik,

In this situation, we’ll need help from the backend team to cancel it on their end. Could you please share the requested details in a Private Message so we can proceed with the next steps?

Answer accepted by question author

Anonymous

Hello Kaushik,

Thank you for your patience as our team addressed the issue.

We coordinated with the backend team and successfully removed the stuck operation.

If the operation still appears as Cancelling, please let us know.

0 comments

1 additional answer

Your answer

Anonymous

2026-05-05T09:42:49.58+00:00

Hi Kaushik,

Thank you for providing the details. The behavior you're experiencing with Run Command is expected in Azure VMware Solution. Run Commands are executed one at a time in the order they're submitted. If a command stays in a “Cancelling” or “Pending” state, it can prevent new commands from running.

To address this, you can try these supported steps:

Retry cancellation in the portal

Open your AVS private cloud in the Azure portal

Go to Operations -> Run command -> Run execution status

Select the affected execution

Click Cancel + delete and confirm

Retry using the Packages view

Navigate to Operations -> Run command -> Packages

Select the relevant package (e.g., Microsoft.AVS.Management)

Go to Run execution status

Find the execution and use More (…) -> Cancel + delete

These steps will try to cancel the execution and remove it after the backend operation is finished.

Allow time for backend processing

After cancelling, wait a bit and refresh the portal

The status might remain “Cancelling” for a while as cleanup completes

If the execution remains stuck

There isn’t a supported way to forcefully remove a run command execution besides the portal actions above

If the state doesn’t change or continues to block new commands, backend assistance is usually needed

Let me know how it turns out for you.

References:

https://learn.microsoft.com/en-us/azure/azure-vmware/using-run-command
Kaushik Srinivas 20 Reputation points

2026-05-11T08:06:25.6366667+00:00

Tried the steps in the earlier comment and i still can see, one run command in cancelling state.
Anonymous

2026-05-12T06:25:08.51+00:00

Hello Kaushik,

In this situation, we’ll need help from the backend team to cancel it on their end. Could you please share the requested details in a Private Message so we can proceed with the next steps?

Answer 1

Kaushik Srinivas hi & thx for join me here at Q&A portal,

queue is wedged, Microsoft needs to clear stuck run-command executions, AVS Run Command queue stuck, not ur script anymore. AVS runs commands one at a time, and i4f one execution stays in Cancelling, new commands stay blocked behind it. try cancel/del from the Run Command blade if available, refresh after 10 15 mins and check Activity Log for the failed/cancelled execution IDs. if portal still shows Cancelling Pending after that, there is no customer-side force clear. open Azure support ticket for Azure VMware Solution Run Command backend cleanup, include private cloud name js-uks-avs-01, stuck command names, timestamps, and screenshot.

rgds, Alex

&

if my answer helps pls accept it.