nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Power Automate Connections Failing

JacobMyers

Hello,

Around 3pm MST yesterday, all of my Power Automate flows started failing. My connections are unable to pull data, even though they still show as connected to my credentials. I added new connections and an API key to see if that would resolve the issue, but I’m still getting the same errors. Here is one example:

“message”: “Fetching data from www.arcgis.com failed. This is usually caused by an invalid authentication token that has expired. Please reauthenticate to continue. Error message: undefined 498: Invalid token.”, “success”: false

Thanks,

Encuentra más publicaciones etiquetadas con

Accepted answers

JacobMyers

Hello -

Seems that ArcGIS AGOL Connections had a small change/update. One neat change is we can name our connections now. Anyway, you can click on Change connection on the bottom of your actions. Create a new one and change them all. Doing this doesn't seem to remove your dynamic inputs (what I was worried about). HOWEVER - it did change my webhook settings for Survey123.

Screenshot 2026-06-03 105927.png

All comments

CodyPatterson

Hey @JacobMyers

Are you able to create a separate Power Automate flow to do something simple like just connect to ArcGIS? If it's still throwing errors, I would check your account to see if it may have been locked out. Do you use a username/password account or another type of authentication?

Cody

abureaux

Did you try re-authenticating? It can look like it's connected even if it isn't. You need to re-authenticate every 2 weeks.

My connections are still working, so shouldn't be a complete blackout. But I am using the Enterprise connectors, so there is always a slim chance there is an AGO issue.

CodyPatterson

To add to this, I tested out AGO connectors and everything's good on my side.

JacobMyers

Hi Cody,

This is AGO fyi not Enterprise - The accounts I use are not locked out. Creating new simple flows with the new connections is inconsistent — But They work. With the new connections, I occasionally get these errors:

Flow save failed with code ‘DynamicOperationRequestClientFailure’ and message: “The dynamic operation request to API ‘arcgis’ operation ‘GetWebhookPayloadSchema’ failed with status code ‘BadRequest’. This may indicate invalid input parameters. Error response: { 'message': 'Info file for item not found:', 'success': false }.”

Another error: “The dynamic schema response from API ‘arcgis’ operation ‘GetWebhookPayloadSchema’ is too large; only schemas with at most ‘1024’ properties are supported.”

For the old connections, all of them show an error similar to the original post. I’ve tried signing in again/ reauthenticate — no change. I also have flows to refresh these connections every hour. I also tried using a new API authentication connection, but I’m seeing similar errors. Overall, my ArcGIS triggers are receiving webhook payloads, but my ArcGIS actions are unable to pull tokens at all and are failing outright.

It seems I have to write all my flows with new connections 😞

XV__

Same problem here:
Failed to retrieve dynamic inputs. Error details: 'The dynamic operation request to API 'arcgis' operation 'QueryFeaturesSchema' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: { "message": "Fetching data from www.arcgis.com failed. This is usually caused by an invalid authentication token that has expired. Please reauthenticate to continue. Error message: undefined 498: Invalid token.", "success": false }'

@AkshayHarshe

JacobMyers

Hello -

Screenshot 2026-06-03 105927.png

tschrage

@JacobMyers

This seems like a solution but I have 60+ flows that use the AGOL connection so changing the connection reference for each one isn't really appealing.

JacobMyers

Same here - I had a lot of critical flows that needed to be addressed quickly, so I was scrambling

Akshay Harshe

@JacobMyers Thanks for your prompt post and other Apologies for inconvenience. We are trying to troubleshoot this issue with Microsoft as there is no reason for existing connections to loose their authentication and have no way to recover. I am glad you were able to quicky resolve this by creating a new connection and updated your flows to make it work. I also outlined the workaround here, which is time consuming if you have a lot of flows using ArcGIS Connection.

:warning: Authentication Issue with ArcGIS Connector (Rel... - Esri Community

Hope this helps.

NICK_COG

We are experiencing the same issue, just started today. We previously had a flow send at 12:30 MST, just failed on a different flow with the same connection at 4:30 PM MST

pangue

Hi we are experiencing the same issue in power automate. The problem just started a few days ago after updating the new ArcGIS connectors. I get an error message when using API Key as well as user/password credentials. I am dynamically loading the feature layer URL as my flow updates 50+ feature layers.

MichaelPierceVAIDSP

I have to question the QA process from ESRi here - if this causes all of its customers to lose their connection references, how was this not caught during QA? Were you only looking for a green status connection indicator or did you actually verify end-to-end transactions were completing successfully?

What changes will you be making to your process so that this isn't repeated - like many others here that caused a multi-day outage that will take a week to recover from. Dozens of flows having to be edited and then a week of data out of sync - no small task. Apologies are nice and all, but I would like to know more about what went wrong and how this is going to be prevented from happening again. Thank you.

RachelAbernethy

Hi everyone - firstly thank you @JacobMyers for raising this issue, it was really helpful to see the conversation last week. Thank you @AkshayHarshe for your quick replies too and your information here: https://community.esri.com/t5/arcgis-connectors-for-power-automate-questions/%EF%B8%8F-authentication-issue-with-arcgis-connector/m-p/1706103#M1352

I also encountered this issue in my customer's environment and we replaced all of the connectors with a new one last week which seemed to resolve the issue. However, we are seeing the same behaviour again today with the flows failing.

Is any one else experiencing this issue again today? I am not sure if there has been another fix or update made to the connectors and perhaps that is causing this?

Thank you
Rachel

Akshay Harshe

@RachelAbernethy Microsoft maybe making some changes, I hope they won't break the new connections that we asked everyone to create. If you go to create a new connection can you see the dropdown to choose between Oauth2 and API Key or no such option?

JacobMyers

@RachelAbernethy All my flows have been down as of yesterday. Around 3pm MST. Both my old connectors before the 2026.2 update and my new ones are giving me similar authentication token errors. From another blog post by @AkshayHarshe - It sounds like Microsoft tried to revert back to 2026.1. Waiting for a solution at this moment.

MarisaTurk

I'm experiencing exactly this today - one week ago, suddenly all our flows began failing with invalid token errors on the connectors despite the connection showing the green 'valid' indicator in the connections list. I created a new connection and swapped it out anywhere the old one was being used (over 20+ flows with 4+ connectors each). This banner sporadically displayed after adding the new connections, but the flows still seemed to work despite it.

Now one week later, exactly the same issue has happened with this new connection - all our flows failing with invalid token errors on the connectors, despite the connection displaying as valid.

Last week I was stuck with updating close to 100 connectors and re-running over 600 failed flows (and will be about the same today). Really hope this doesn't continue happening!

NICK_COG

My connections broke again today and I did not see the auth type dropdown.

jlng0001

I did the exact same steps and it worked for about a week since 6/4/2026 and I am getting the same error even I have recreate all connections, connection references and the ArcGIS connectors.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.