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 / Custom Connector loses...
Power Automate
Suggested Answer

Custom Connector loses code every time you edit

(1) ShareShare
ReportReport
Posted on by 2
This is the most ridiculously terrible interface I have ever seen. If you click Edit on a custom connector, any code you entered or uploaded is immediately wiped. If you click Edit simply so you can test your connector, the code is wiped and you have to re-upload it and update your connector. If you click Edit just to modify the icon for your custom connector, the code is wiped and has to be re-uploaded. This is absolutely pathetic.
I have the same question (0)
  • Suggested answer
    Haque Profile Picture
    1,440 on at
    Hi @CD-02041845-0
     
    This is a kind of known frustration reported by users. This happens because the Power Automate custom connector editor currently does not fully preserve custom code or uploaded files when we open the connector for editing, especially if we make changes unrelated to the code itself (like changing the icon or just opening the editor to test).
     
    Let's investigate the reason: 

    The custom connector editor in  primarily manages the connector’s OpenAPI (Swagger) definition and metadata. Opening the editor, it reloads the connector definition from the stored OpenAPI JSON. If the custom code or uploaded files are not properly embedded or saved as part of the OpenAPI definition, the editor may reset or clear them! Editing non-code properties (like icons) triggers a save operation that overwrites the connector definition, causing the code to be lost. This is a limitation of the current (PA) custom connector UI and how it handles custom code or uploaded files. 

    Things to tackle:

    1. Let's avoid modifying the edirot for minor stuff like icons. (I am sorry why we need to do that? - Actually finding no other way)

    2. Let's keep custom code outside the connector eidtor - maintain code in a separate file or source control. Before editing the connector, export or back up code. After editing, re-import or paste the code back. (tedious but effective).

    3.  Let's report feedback to MS - this is a know UX limitation. Providing feedback through official channels may help prioritize improvements.

     

    I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

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!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 605

#2
Valantis Profile Picture

Valantis 340

#3
11manish Profile Picture

11manish 284

Last 30 days Overall leaderboard