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

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Unable to use PowerAut...
Power Automate
Answered

Unable to use PowerAutomate - InternalServerError on main page

(0) ShareShare
ReportReport
Posted on by 15
I am unable to access the "Flows" home page and to create new flows. This has been the case since around the month of May.
 
 
 
The error is shown in the Flows homepage (see below) is:
 
 
InternalServerError

Http request failed with unhandled exception of type 'ArgumentException' and message: 'An item with the same key has already been added.'.
 
 
 
If I access the solution and click on the specific flow it never stops loading (see below)
 
 
If I click on Edit, this is what shows up:
 
 
 
Accessing a specific flow is impossible as I can't reach the edit page of the flow. Even trying Classic mode, or logging in with different browsers and in anonymous tabs or using other computers yield the same result.
 
 
 
I suspect this flow has two actions with the same name. Would it be possible for an engineer rename this duplicate action so I can have access to PowerAutomate again?
 
 
 
Just to reiterate, I am unable to create new flows or edit them, my account is unable to be used in its current state.
Categories:
I have the same question (0)
  • mapledesk Profile Picture
    15 on at
    I am really hoping for some help here. Or at least an update on this issue. What else could I do? I'm taking any advice, please help.
  • Suggested answer
    CFernandes Profile Picture
    8,482 Most Valuable Professional on at
    Hey @mapledesk , This looks like a temporary problem. Please check the Service Status https://learn.microsoft.com/en-us/power-platform/admin/check-online-service-health
     
    If your service status looks all good, clear the browser cache and try again. 
     
    Microsoft 365 admin center service health dashboard.
     
    If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
     
    P.S. take a look at my blog here and like & subscribe to my YouTube Channel thanks.
     
     
  • CFernandes Profile Picture
    8,482 Most Valuable Professional on at
    Hey @mapledesk There was a service Intruption on the day you reported. The problem should now be resolved.
  • mapledesk Profile Picture
    15 on at
    Thank you for the replies @CFernandes,
     
    There was a change to something as now I am able to open the home page, but the error is still there when I access the problematic flow. The flow never loads and editing it does not work and yields the same result:
     

    If you contact support, you may be asked to provide the following details:

    Time: "2025-01-02T14:25:52.284Z"
    Session ID: 4860e2e0-c915-11ef-bb87-39a013a867f4
    x-ms-client-request-id (Client->Backend Request Header): 69dedb2c-fa6a-4f60-a5b4-7926bc29d54a
    x-ms-correlation-request-id (Backend Response Header): c55955ed-43ae-4862-8bcc-2734fcd36e1c
    Error: Http request failed with unhandled exception of type 'TemplateValidationException' and message: 'The template trigger and action names must be unique. The flow with name '<null>' was found to have duplicate action names: 'Terminate_on_unexpected_state'.'.
     
    I see no issues on the service health when looking through a domain admin account. I searched for "TemplateValidationException" on Known Issues and I have found no related issue under Power Automate.
    I created a ticket with Microsoft about 9 months ago and stopped receiving updates on the matter.
    What else could I do to help myself getting out of this issue?
     
    FlowName: 53b2d08b-169e-f53c-4b59-f1e55850e2a4
    WorkflowEntityId: 8e1aa8c6-09e3-ee11-a204-000d3af47f27
  • Verified answer
    mapledesk Profile Picture
    15 on at
    I was able to figure out a way out of this.
     
    The issues were being caused by a duplicate action name in the same flow, so I did this:
    1. Export the solution that has the problematic flow
    2. Extract all files to a directory
    3. Open the problematic flow (it's under the "Workflows" folder) with a text editor
    4. Find the action with duplicate names
    5. Change the name (in my case they were under an "actions" object)
    6. Zip the contents of the folder (there should be .XML files in the root of the zipped file)
    7. Import the solution back into Power Automate
    I had asked Microsoft support multiple times if this could be resolved by simply doing this process remotely as I was not aware I could have done this, I was told this was an issue with Power Automate servers all the times. It is unfortunate that I was not guided on doing this 9 months ago.
     

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 124 Super User 2026 Season 1

#2
Ellis Karim Profile Picture

Ellis Karim 52 Super User 2026 Season 1

#3
Expiscornovus Profile Picture

Expiscornovus 47 Most Valuable Professional

Last 30 days Overall leaderboard