Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Automate - Using Flows
Unanswered

Persistent "Unable to Fetch" errors when troubleshooting flows

(0) ShareShare
ReportReport
Posted on by 20

I'm trying to troubleshoot failed flows and am getting persistent "Unable to fetch" errors when opening action connectors, which provides a URL and ends saying "Too many requests". This isn't a temporary problem - it's been ongoing for a whole year now, I've posted a community message in the past which attracted zero response (might have been a service account rather than my personal one).

 

I'm desperate. This issue is making the platform unusable. I cannot find any guidance around this issue, have no way to resolve. I'd even take a weird workaround. I have no way to find out what the issue is because the 'topline' error in the 'Help' panel is too generic, and I cannot open up the failing action because I hit an unable to fetch on a Switch which prevents the switches opening up.

  • SimonLavisUOS Profile Picture
    20 on at
    Re: Persistent "Unable to Fetch" errors when troubleshooting flows

    Appreciate you taking the time anyway, Mike, thanks!

  • Michael E. Gernaey Profile Picture
    41,020 Super User 2025 Season 1 on at
    Re: Persistent "Unable to Fetch" errors when troubleshooting flows

    Hi Simon,

     

    I am so sorry this is such a bad situation. I really think at this point you should contact support directly, as if its as you explain, all of them with no good direction, you will need support to look at the back end to find out why its happening, as thats where the errors are coming from.

     

    Very  very weird indeed.
    Cheers
    If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
    Thank You
    Michael Gernaey MCT | MCSE | Ex-Microsoft
    https://gernaeysoftware.com
    LinkedIn: https://www.linkedin.com/in/michaelgernaey

  • SimonLavisUOS Profile Picture
    20 on at
    Re: Persistent "Unable to Fetch" errors when troubleshooting flows

    Hi @FLMike, thanks for replying!

     

    • Can I ask which connectors you are trying to use? - all sorts, and it's not restricted to certain flows. I use a lot of Excel, SharePoint connectors (get item(s)/get rows; updates, creates etc.), a few premium (HTTP actions and the When HTTP Request is Received trigger, lots of Data Operation actions (filters, selects, composes); increasingly using array variables which I (re)set, append to in ATE's. And a fair few controls (Conditions, ATE, Switches). And once the issue is triggered (I can normally open up 2-4 actions before it starts) it impacts most triggers indiscriminately. The only thing to note re: connectors is that once this begins, it prevent expanding Switch conditions, so cannot troubleshoot errors within very easily. 
    • Is there a gateway or VPN involved between the connector and the endpoint? - typically I work on devices going through a gateway, but I think I can rule this out as the problem also occurs on my personal device without gateway/VPN on multiple connections including home internet and cellular via the Automate app... also, when I tried the following suggestion about re-adding a new connection, there was a tickbox for gateway there which I ignored and clicked the sign in option to create a new one; however, after reviewing the connections section afterwards, whilst I don't have the option to change the setting (they're greyed out), all existing and new connections are cloud-based, not via gateway. 
    • Have you tried to remove the connection from the details page and readd it or create a new one in its place? - I hadn't, as I'd assumed with it not discriminating against any particular connectors that it wasn't the issue; however, I've just done thorough and reestablished all connections in the set of flows I'm working on, and rerun, and the problem remains (also this has been ongoing over two service accounts I use).
    • Is this a production deployment? - I'm afraid I don't know this term so I suspect not, but cannot be certain. 
    • Have you created a new flow, that uses the exact same connector reference? to see if that causes the same problem or are other flows, that use that connector and or exact connector reference ok? - other way around, I've created entirely new flows doing different jobs, and in a different account so it's not using the same 'connection'. 
    • Have you tried to recreate the flow? - no, but again this is impacting unconnected flows in the same way. 
    • Have you tried to remove it (export), and reimport it? - no
    • have you added in or do you have error handling that might catch the real error and tell you what it is, or doe s it just fail, but not caught by a block in your flow? - I don't have error handling per se, no. I can see in the 'Run Details' tab which action fails, but 95% of the time I cannot get deep enough into the flow before the error begins. 

    I can rule out device (multiple laptops, and 2 IOS devices using the app), browser (Chrome regular and Chrome  Incognito (no cookies); Firefox regular and Firefox Private tab; Edge; Safari on iPad; plus it's impacting the Automate IOS app too), VPN/gateway, connector. I'm at a loss.  

  • Michael E. Gernaey Profile Picture
    41,020 Super User 2025 Season 1 on at
    Re: Persistent "Unable to Fetch" errors when troubleshooting flows

    Hello,

     

    • Can I ask which connectors you are trying to use?
    • Is there a gateway or VPN involved between the connector and the endpoint?
    • Have you tried to remove the connection from the details page and readd it or create a new one in its place?
    • Is this a production deployment? 
    • Have you created a new flow, that uses the exact same connector reference? to see if that causes the same problem or are other flows, that use that connector and or exact connector reference ok?
    • Have you tried to recreate the flow?
    • Have you tried to remove it (export), and reimport it?
    • have you added in or do you have error handling that might catch the real error and tell you what it is, or doe s it just fail, but not caught by a block in your flow?

    I have been seeing some issues for folks who are going through gateways (hence my one question). But sometimes You may just have the bad luck of a connector, or connector reference gone wrong.

     

    Not sure what you are have tried in the past, but I am open to try to help you.

     

    Cheers
    --------------------------------------------------------------------------------
    If I had answered your question, please mark your post as Solved
    If you like my post please give it a thumbs up
    Thanks
    Michael
    https://gernaeysoftware.com

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

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Markus Franz – Community Spotlight

We are honored to recognize Markus Franz as our April 2025 Community…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,645 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 65,997 Most Valuable Professional

Leaderboard

Featured topics

Restore a deleted flow