web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / The workflow in subscr...
Power Automate
Suggested Answer

The workflow in subscription and resource group 'selfhostingresourcegroup' is currently locked

(0) ShareShare
ReportReport
Posted on by 2,015 Season of Giving Solutions 2025
I am trying to enable or save an automate flow, but i am getting this error:-


The workflow '70ad9987-ce8b-4706-902e-ae4befa68eb7' in subscription '4f36630d-ee46-e9cd-85bc-5b25fec5240f' and resource group 'selfhostingresourcegroup' is currently locked. Please try again shortly.
 
 
 
I have the same question (0)
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    2,318 Moderator on at
     

    This error means the Power Automate workflow resource is temporarily locked on the Azure side, not that there is a problem with your flow logic.

    What’s happening

    Power Automate runs on Azure Logic Apps infrastructure. A workflow can become locked while:

    • It is still deploying or updating
    • Another save, publish, or run operation is in progress
    • The flow is being modified by another user or session
    • Azure is performing background maintenance on the resource group

    During that time, saves and enables are blocked.

    What to try (in order)

    1. Wait a few minutes and refresh
      This is often a short‑lived lock that clears on its own.

    2. Confirm no one else is editing the flow
      Ask teammates to close the flow if it is open elsewhere.

    3. Check if the flow is currently being saved or deployed

      • If the designer shows “Saving…” for a long time, close the browser tab and reopen the flow.
      • Avoid multiple Save clicks or parallel edits 
    4. Disable, wait, then re‑enable
      If the flow opens, try disabling it, wait 1–2 minutes, then enable again.

    5. Check Azure resource locks (less common but possible)

      • Go to the Azure portal
      • Open the resource group selfhostingresourcegroup
      • Ensure there is no ReadOnly or Delete lock applie 
    6. Clear stuck runs
      If the flow has long‑running or stuck executions, cancelling them can release the lock.

    When to escalate

    If the lock persists for more than 30–60 minutes, this is usually an Azure backend issue. Open a Microsoft support ticket and reference:

    • Subscription ID
    • Resource group
    • Workflow ID shown in the error

    Bottom line

    This is a platform‑level lock, not a configuration mistake. In most cases, waiting a short time or reopening the flow resolves it.

    ✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
    👍 Feel free to Like the post if you found it useful.

    Sunil Kumar Pashikanti, Moderator
    Blog:
     https://sunilpashikanti.com/posts/
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard