Azure Cache for Redis scale-down stuck in "Scaling" state for days, all subsequent updates fail

Julien Iseli 0 Reputation points
2026-07-15T07:55:33.3966667+00:00

We have an Azure Cache for Redis instance.

A scale-down operation from Premium P3 to Premium P1 was initiated on 2026-07-09 13:59 CEST. The operation was accepted successfully and the Activity Log shows "Update Redis Cache - Accepted", but the cache has remained in a Scaling state ever since.

Since then, any attempt to perform additional updates on the cache fails because Azure reports that another operation is already in progress. The Activity Log contains multiple "Update Redis Cache - Failed" entries following the original accepted request.

Questions

  1. Is there a way to determine whether the backend scaling operation is stuck?
  2. Can a scaling operation be cancelled or reset?
  3. Is Microsoft able to recover the resource if the operation is blocked indefinitely?
  4. Are there known issues with Premium cache scale-down operations becoming stuck for extended periods?

I can provide:

  • Activity Log screenshots
  • Operation ID / Correlation ID
  • Resource JSON
  • Current provisioning state

Any guidance would be appreciated.

Azure Cache for Redis
Azure Cache for Redis

An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.

2 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Christos Panagiotidis 3,551 Reputation points
    2026-07-15T08:09:34.0933333+00:00

    A Premium scale operation can take time, but six days in Scaling with every later update rejected is not a normal wait state. There is no supported customer action in the portal or CLI to cancel or reset an accepted cache scale operation; retrying updates will not clear it.

    Confirm the current state with:

    az redis show -g <resource-group> -n <cache-name> --query provisioningState -o tsv

    Then open an Azure support request and provide the cache resource ID, the original operation/correlation ID, and the failed Activity Log events. Support can inspect the service-side operation and perform the required recovery; Q&A cannot unblock that control-plane operation.

    Until it is resolved, avoid further configuration or scaling changes. If continuity is critical, plan a separate cache migration/failover only with an explicit data and client-connection cutover plan; do not delete the affected cache as a workaround.

    Was this answer helpful?

  2. SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator
    2026-07-29T14:53:07.17+00:00

    Hi @Julien Iseli ,

    Here is a summary of the key points from our case for your records:

    Issue: Redis Cache Failure

    Analysis and Resolution: Upon reviewing the issue, we analyzed the backend configurations and engaged the Microsoft Product Group (PG) team for further investigation. The engineering team identified the underlying issue affecting the cache instance and successfully performed the necessary backend mitigation actions.

    Following the mitigation, the cache was restored to a healthy and active state. We verified that the service is now functioning as expected, and you subsequently confirmed that the issue has been resolved.

    Further References: As an added benefit, you may find the following Azure resource helpful for staying informed about platform updates and announcements:

    1. Important Azure Updates: Azure Updates

    Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

    Was this answer helpful?

    0 comments

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.