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 Automate
Suggested Answer

Erro de conexão

(2) ShareShare
ReportReport
Posted on by 5
Hi everyone, I am new to the group. I am having a problem with the definition in an automation due to the connection. Here the environment was migrated to Azure, which ended up resulting in the need to create a new gateway and update the connections to access the APIs in the new environment. Now my connections and custom connections are giving errors. I have redone them but I still have problems with the automation connections.
Categories:
I have the same question (0)
  • Vish WR Profile Picture
    2,292 on at
     
    Can you provide screenshot and what error you are getting?
  • Suggested answer
    11manish Profile Picture
    2,126 on at
    Recreating connections alone is not enough. You must rebind the full chain:
     
    Flow → Connection Reference → Connection → Gateway → API
     
    If any layer still points to the old setup, the automation will fail.
  • Suggested answer
    Sunil Kumar Pashikanti Profile Picture
    2,069 Moderator on at
     
    After migrating to Azure and recreating the On‑premises Data Gateway, existing Power Automate flows often keep stale connection references. Even if you recreate connections/custom connectors, flows will continue to fail until every action is explicitly re‑bound to the new gateway/connection and the custom connector definition is refreshed and republished.
     
    Common root causes & fixes

    1)Gateway mismatch
    Connections still point to the old gateway ID.
    Fix: Recreate the connection selecting the new gateway, then edit the flow and reselect the connection on every action.
     
    2)Stale connection references in flows
    Flow actions cache the old connection.
    Fix: Open each action → reselect the connection (don’t rely on “fix connection” at the flow level).
     
    3)Custom connector not republished
    After environment/API changes, old Swagger/host URLs remain.
    Fix: Update the custom connector (host, base URL, auth), Save → Update connector → Republish, then recreate the connection.
     
    4)Authentication changes
    API auth type changed (Basic ↔ OAuth ↔ API Key), cert rotated, or credentials expired.
    Fix: Verify auth settings in the connector; re‑enter secrets; confirm scopes/headers.
     
    5)Environment variables still pointing to old endpoints
    Especially with solutions.
    Fix: Update environment variables and re‑import / upgrade the solution.
     
    6)Gateway permissions
    New gateway installed but service account not authorized.
    Fix: Add the account as a Gateway Admin/User and ensure firewall/ports are open.

    Quick validation steps
    Test the connection itself (not just the flow).
    Create a new test flow using the same connector, if it works, the old flow still has cached refs.
    Check Run History → Action error details for gateway/host/auth hints.

    Conclusion:
    Recreating the gateway/connections is necessary but not sufficient. You must republish custom connectors and rebind every flow action to the new connections/gateway. This resolves most “connection error after Azure migration” issues.
     
    ✅ 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/
  • Suggested answer
    Valantis Profile Picture
    4,895 on at
     
    A few things would help narrow this down fast.

    What is the exact error message you see when the flow runs or when you try to save it? And are these flows failing because the connection shows a red error icon inside the flow itself, or does the connection look fine in the connections page but the flow still fails at runtime?

    The most common issue after recreating connections is that each flow still internally references the old connection by ID. Creating a new connection in the connections page doesn't automatically update the flows — you have to open each flow, go into the action that uses that connection, and manually reselect the new connection from the dropdown. Until you do that, the flow keeps trying to use the old broken connection even if it no longer exists.
     

     

    Best regards,

    Valantis

     

    ✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

    ❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

    🏷️ For follow-ups  @Valantis.

    📝 https://valantisond365.com/

    💼 LinkedIn

    ▶️ YouTube

  • Valantis Profile Picture
    4,895 on at

    Hi @SF-16011220-0,

    Just wanted to check in and see if everything is working now. If you still need any help, feel free to let me know.

    Also, if the issue is resolved, it would be great if you could mark the answer as solved so others with the same question can find it easily.

     

    Thanks and have a great day!

     

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
Vish WR Profile Picture

Vish WR 881

#2
Valantis Profile Picture

Valantis 823

#3
Haque Profile Picture

Haque 485

Last 30 days Overall leaderboard