Share via

Operation timed out while deploying application gateway after multiple retries.

Joshua Jiji (Centific Technologies Inc) 0 Reputation points Microsoft External Staff
2026-06-03T20:16:46.3266667+00:00

Trying to upgrade our clusters but stuck at one application deployment. The operation timed out while deploying application gateway after multiple retries.

Below is the error it gives:

{

"code": "GwmOperationTimeOut",

"message": "Operation timed out. Please retry after some time or contact support.",

"details": []

}.

Azure Application Gateway
Azure Application Gateway

An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.


Answer accepted by question author

Venkatesan S 8,490 Reputation points Microsoft External Staff Moderator
2026-06-03T20:51:06.0566667+00:00

Hi Joshua Jiji (Centific Technologies Inc),

Thanks for reaching out in Microsoft Q&A forum,

The GwmOperationTimeOut error indicates that the Application Gateway operation did not complete within the expected timeframe. This can occur when a previous gateway update is still in progress, when multiple operations target the same Application Gateway, or when the resource provider encounters delays processing the request.

Steps:

  1. Check the provisioning state
       az network application-gateway show \
       --resource-group <resource-group> \
       --query "{provisioningState: provisioningState, operationalState: operationalState}"
    
    Look for Updating, Failed, or Succeeded.
  2. Review the Activity Log Azure Portal > Application Gateway > Activity log > Filter by Failed events > Check the statusMessage in JSON view for the root cause (SSL cert, backend pool, WAF policy, etc.).
  3. Check for concurrent operations Multiple deployments to the same gateway can cause later operations to wait or fail. If another operation is in progress, wait 15–30 minutes before retrying.
  4. Retry after verifying no active operation If the gateway has been in Updating state for an extended period with no progress, retry the deployment.
  5. Optional: Harmless configuration refresh If the gateway appears stuck and no active deployment is progressing, updating a tag can sometimes trigger a fresh PUT operation and help recover the resource state:

Azure CLI:

   az network application-gateway update \
  --name <gateway-name> \
  --resource-group <resource-group> \
  --set tags.reset="reset-$(date +%s)"

Powershell:

   $gw = Get-AzApplicationGateway -Name <gateway-name> -ResourceGroupName <resource-group>
   Set-AzApplicationGateway -ApplicationGateway $gw

PowerShell note: Set-AzApplicationGateway -ApplicationGateway $gw pushes the full configuration back to Azure. Review pending changes before executing.

Reference:

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to 210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

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